Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enable landlock selftests on BeagleBone Black #1507

Closed
wants to merge 1 commit into from
Closed

Enable landlock selftests on BeagleBone Black #1507

wants to merge 1 commit into from

Conversation

broonie
Copy link
Member

@broonie broonie commented Nov 10, 2022

Enable landlock selftests on BeagleBone Black

@broonie broonie mentioned this pull request Nov 10, 2022
Merged
@nuclearcat nuclearcat mentioned this pull request Nov 21, 2022
Merged
@mgalka
Copy link

mgalka commented Nov 22, 2022

It looks there are kernel panics on boot:

https://storage.staging.kernelci.org/kernelci/staging-mainline/staging-mainline-20221120.0/arm/multi_v7_defconfig+kselftest/clang-11/lab-broonie/kselftest-landlock-beaglebone-black.html#L823

https://storage.staging.kernelci.org/kernelci/staging-mainline/staging-mainline-20221121.0/arm/multi_v7_defconfig+kselftest/clang-11/lab-broonie/kselftest-landlock-beaglebone-black.html#L823

@nuclearcat
Copy link
Member

Yes, this is expected, arm64 boards have issues on their own(not related to landlock) as seems many of them have boot issues recently, this is why i added x86 chromebook to prove that landlock test itself is working.

@nuclearcat nuclearcat self-assigned this Jan 3, 2023
@nuclearcat
Copy link
Member

I am adding +kselftest kernels to baseline tests, because it looks like such kernels have bootability issues on this board.
This is likely affecting also: #1506
#1505

Relevant PR: #1606

@broonie
test-configs.yaml: Run landlock on BeagleBone Black
5ef90cf 
We have a relatively large set of BeagleBone Blacks (even more once I get
the 5 I've got sitting waiting plugged in) so should have the capacity and
it gives us 32 bit coverge.

Signed-off-by: Mark Brown <broonie@kernel.org>
@gctucker
Copy link
Contributor

gctucker commented Apr 6, 2023

@broonie Could you please take a look?

@mgalka
Copy link

mgalka commented Apr 6, 2023

More up to date results from staging - still panicking

https://storage.staging.kernelci.org/kernelci/staging-next/staging-next-20230330.2/arm/multi_v7_defconfig+kselftest-slim/clang-17/lab-broonie/kselftest-landlock-beaglebone-black.html#L679

@gctucker
Copy link
Contributor

This also relies on smaller kselftest builds, see #1759.

@gctucker
Copy link
Contributor

gctucker commented Jul 5, 2023

Adding skip label because of #1994

@gctucker gctucker added the staging-skip Don't test automatically on staging.kernelci.org label Jul 5, 2023
@l0kod
Copy link

l0kod commented Oct 13, 2023

Any news? How can we help?

@broonie
Copy link
Member Author

broonie commented Oct 13, 2023

We'll at least need #2117 resolving so we're running things on 32 bit Arm again - I don't know if the upstream changes I made (I got some of the worst instrumentation disabled) have mitigated the size issues to the point where we can boot the full kselftest kernel on the boards.

@nuclearcat
Copy link
Member

Closing, as we are deprecating the legacy system. If this is still an issue or relevant, please re-open it under the Maestro system. Thank you for your contribution, and sorry for the inconvenience.

@nuclearcat nuclearcat closed this Jul 16, 2024
@l0kod l0kod mentioned this pull request Jul 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@nuclearcat nuclearcat

Labels
staging-skip Don't test automatically on staging.kernelci.org
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@broonie @mgalka @nuclearcat @gctucker @l0kod