[20.10 backport] seccomp: always allow name_to_handle_at(2) #45835
Conversation
This file contains 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
Signed-off-by: Vitor Anjos <[email protected]> (cherry picked from commit fdc9b7c) Resolved conflicts: profiles/seccomp/default_linux.go Co-Authored-by: Bjorn Neergaard <[email protected]> Signed-off-by: Bjorn Neergaard <[email protected]>
bartier
approved these changes
Jun 27, 2023
Based on the analysis on [the previous PR][1]. [1]: moby#45766 (review) Signed-off-by: Bjorn Neergaard <[email protected]> (cherry picked from commit b335e3d) Resolved conflicts: profiles/seccomp/default_linux.go Signed-off-by: Bjorn Neergaard <[email protected]>
neersighted
changed the title
|
@corhere Are you okay with bringing this back to 20.10? |
corhere
approved these changes
Jun 28, 2023
|
Vendor issue is a flake. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #45518
Hi there, this is my first PR here, so please feel free to point me out if anything is wrong with this contribution. I looked the #45518 issue and I believe this could be a fix.
- What I did
Removed the function from the filtered syscalls as
name_to_handle_at(2)is in fact innocuous and safe- How I did it
@neersighted help at comment
- How to verify it
N/A
- Description for the changelog
Remove name_to_handle_at(2) from filtered syscalls
- A picture of a cute animal (not mandatory but encouraged)
