Repository navigation
kernel: strike the BPF_LSM note the guard replaced - #102
Merged
Merged
Conversation
The lockdown commit enabled CONFIG_SECURITY and CONFIG_BPF_LSM and guarded both above the BPF section, with the reason beside the guard. The note here still says BPF_LSM is off and why somebody would switch it on: the decision it records has been made, by the guard, and the two now disagree in one file. A build cannot read either; the build reads the guard.
aledbf
force-pushed
the
f2b/stale-bpf-lsm-note
branch
from
October 5, 2026 04:46
15771a4 to
8c1bd44
Compare
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.
F2b's lockdown commit (1400f6a) enabled CONFIG_SECURITY and CONFIG_BPF_LSM and guards both above the BPF section, with the reason beside the guard. The note in the BPF section still records the opposite decision — that BPF_LSM is deliberately off and somebody would have to switch it on "deliberately, with a measurement" (it even says CONFIG_SECURITY is off, which is no longer true of the config in the same build).
A build reads the guard. The note now only disagrees, so it goes. One line of build-script prose, no behaviour.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.