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.

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

Add support for containers #4

Merged
merged 11 commits into from
May 13, 2024
Merged

Add support for containers #4

merged 11 commits into from
May 13, 2024

Conversation

l0kod
Copy link
Member

@l0kod l0kod commented Apr 4, 2024

This will make easier to use specific tools (e.g. linters) and test against different distros.

This was referenced Apr 4, 2024
README.md Outdated Show resolved Hide resolved
@l0kod
Copy link
Member Author

l0kod commented Apr 9, 2024

I'm holding this PR for now because tests don't pass with the latest kernel. It's related to landlock-lsm/linux@0710a1a (and landlock-lsm/linux@41cca05), because of private mount points.

Don't use `git checkout` to not need to create index.lock, because the
repository (but not the worktree) is read-only.

Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
@l0kod
Copy link
Member Author

l0kod commented Apr 29, 2024

@l0kod l0kod marked this pull request as ready for review April 30, 2024 13:46
srcres258 pushed a commit to srcres258/linux-doc that referenced this pull request May 7, 2024
According to the test environment, the mount point of the test's working
directory may be shared or not, which changes the visibility of the
nested "tmp" mount point for the test's parent process calling
umount("tmp").

This was spotted while running tests in containers [1], where mount
points are private.

Cc: Günther Noack <[email protected]>
Cc: Shuah Khan <[email protected]>
Link: landlock-lsm/landlock-test-tools#4 [1]
Fixes: 41cca05 ("selftests/harness: Fix TEST_F()'s vfork handling")
Reviewed-by: Kees Cook <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mickaël Salaün <[email protected]>
kuba-moo pushed a commit to linux-netdev/testing that referenced this pull request May 12, 2024
According to the test environment, the mount point of the test's working
directory may be shared or not, which changes the visibility of the
nested "tmp" mount point for the test's parent process calling
umount("tmp").

This was spotted while running tests in containers [1], where mount
points are private.

Cc: Günther Noack <[email protected]>
Cc: Shuah Khan <[email protected]>
Link: landlock-lsm/landlock-test-tools#4 [1]
Fixes: 41cca05 ("selftests/harness: Fix TEST_F()'s vfork handling")
Reviewed-by: Kees Cook <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mickaël Salaün <[email protected]>
@l0kod
Copy link
Member Author

l0kod commented May 13, 2024

I'm holding this PR for now because tests don't pass with the latest kernel. It's related to landlock-lsm/linux@0710a1a (and landlock-lsm/linux@41cca05), because of private mount points.

Fixed in Linux 6.9 with landlock-lsm/linux@af300a3

l0kod added 9 commits May 13, 2024 07:46
Old setpriv doesn't support +all capabilities, so generate and use the
explicit list of supported capabilites instead.

Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
We now support clang-format between version 14 and 17 included.

Signed-off-by: Mickaël Salaün <[email protected]>
This is simpler and it enables concurrent use of the same image.

Signed-off-by: Mickaël Salaün <[email protected]>
Signed-off-by: Mickaël Salaün <[email protected]>
@l0kod l0kod merged commit 8e81af7 into landlock-lsm:main May 13, 2024
@l0kod l0kod deleted the docker branch May 13, 2024 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants