chmod: do not check umask on skipped symlinks during recursion - #14512
Merged
Merged
Conversation
okaythi
force-pushed
the
fix/chmod-recursive-symlink-umask
branch
from
September 12, 2026 08:53
2e59b48 to
dbc75f3
Compare
|
GNU testsuite comparison: |
Contributor
|
Thanks |
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
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.
When running
chmod -R -w, skipped symlinks fell through to the umask validation check and triggered a bogusnew permissions are ...error.Fixed by returning early with
Ok(())when skipping symlinks reached without dereferencing inchmod_file_internal.Fixes Ubuntu Launchpad bug #2167122.