vm: enable Landlock in both guest kernels - #35
Open
zbarsky-openai wants to merge 1 commit into
Open
zbarsky-openai wants to merge 1 commit into
zbarsky-openai wants to merge 1 commit into
Conversation
Sandbox tests executed inside actiond fail because its minimal guest kernels do not implement the Landlock system calls: ```text landlock.SyscallError: [Errno 38] Function not implemented: 'Error calling landlock_create_ruleset: syscall(444, None, 0, 1) = -1' Note: Cannot find Landlock syscalls - perhaps the kernel was not built with 'CONFIG_SECURITY_LANDLOCK=y' RuntimeError: Landlock not available in linux kernel, unable to create a safe sandbox. ``` Enable the kernel security framework and Landlock on both ARM64 and x86_64, and explicitly select Landlock in the boot-time LSM list. Linux automatically selects the required security-path and networking hooks. Both fragments were resolved through the repository's actual Linux 6.18.2 Kconfig parser with `allnoconfig`, verifying `CONFIG_SECURITY`, `CONFIG_SECURITY_LANDLOCK`, `CONFIG_SECURITY_PATH`, `CONFIG_SECURITY_NETWORK`, and `CONFIG_LSM` for both architectures. The original failure was reproduced remotely with `//project/oai_sandbox:pytest -k test_seccomp_default_action`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sandbox tests executed inside actiond fail because its minimal guest kernels do
not implement the Landlock system calls:
Enable the kernel security framework and Landlock on both ARM64 and x86_64,
and explicitly select Landlock in the boot-time LSM list. Linux automatically
selects the required security-path and networking hooks.
Both fragments were resolved through the repository's actual Linux 6.18.2
Kconfig parser with
allnoconfig, verifyingCONFIG_SECURITY,CONFIG_SECURITY_LANDLOCK,CONFIG_SECURITY_PATH,CONFIG_SECURITY_NETWORK,and
CONFIG_LSMfor both architectures. The original failure was reproducedremotely with
//project/oai_sandbox:pytest -k test_seccomp_default_action.The ARM64 kernel was then built through actiond itself (
//vm:linux_kernel.image; 924 real remote compilation actions, followed by a successful 25-remote-action relink after repairing one pre-existing corrupt CAS blob). The rebuilt kernel boots successfully, and the original sandbox test now passes its Landlock ABI check and reaches the separate missing-libcap.so.2dependency.