vm: enable /proc/sys in both guest kernel configurations - #45
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
actiond's minimal `allnoconfig` Linux kernels omit `/proc/sys` altogether. A
real actiond-executed probe currently fails with:
```text
{"sysctl": "/proc/sys/kernel/hostname", "errno": 2}
FileNotFoundError: [Errno 2] No such file or directory:
'/proc/sys/kernel/hostname'
```
Enable `CONFIG_PROC_SYSCTL=y` in both ARM64 and x86_64 kernel configurations.
Linux's existing `PROC_SYSCTL` option selects the underlying `SYSCTL` support;
no runtime package is added. Existing procfs mounts then expose the standard
kernel settings interface while retaining the current unprivileged action,
seccomp, Landlock, and disabled-BPF-JIT protections.
Validated by rebuilding the ARM64 guest through actiond itself (974 actual
remote actions; `0807aacd-7c6d-43ca-a75c-271eebdb6ceb`), booting that kernel,
and confirming `/proc/sys/kernel/hostname` is readable while nested seccomp
filter installation still succeeds (`d40ec092-87c4-4a13-a4a7-5b92e9cb1a0f`).
The production sandbox suite then passed with 191 tests and 10 expected skips
under the real actiond executor (`f6788d1f-8b3d-459c-87b8-bf5efd588496`).
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.
actiond's minimal
allnoconfigLinux kernels omit/proc/sysaltogether. Areal actiond-executed probe currently fails with:
Enable
CONFIG_PROC_SYSCTL=yin both ARM64 and x86_64 kernel configurations.Linux's existing
PROC_SYSCTLoption selects the underlyingSYSCTLsupport;no runtime package is added. Existing procfs mounts then expose the standard
kernel settings interface while retaining the current unprivileged action,
seccomp, Landlock, and disabled-BPF-JIT protections.
Validated by rebuilding the ARM64 guest through actiond itself (974 actual
remote actions;
0807aacd-7c6d-43ca-a75c-271eebdb6ceb), booting that kernel,and confirming
/proc/sys/kernel/hostnameis readable while nested seccompfilter installation still succeeds (
d40ec092-87c4-4a13-a4a7-5b92e9cb1a0f).The production sandbox suite then passed with 191 tests and 10 expected skips
under the real actiond executor (
f6788d1f-8b3d-459c-87b8-bf5efd588496).