Only try to apply grsec_lock once #7353
Merged
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.
Status
Ready for review
Description of Changes
Currently we specify both
sysctl_set: yes
andreload: yes
when setting sysctl settings, which ends up with it being applied twice, first withsysctl -w
(sysctl_set) and then throughsysctl -p
(reload).With noble/Linux 6.6, setting the lock twice errors out, so just enable it once with
sysctl -p
. This is also closer to what the kernel will do normally when booting in which the whole file is loaded at once.Refs #7323.
Testing
How should the reviewer test this PR?
Deployment
Any special considerations for deployment? only affects new installs, which is where the bug is
Checklist