SELinux: allow to query attrs of a filesystem#10726
Merged
Conversation
oxzi
approved these changes
Mar 31, 2026
Member
oxzi
left a comment
oxzi
left a comment
There was a problem hiding this comment.
Unfortunately, I was unable to reproduce the reported issue. However, the change looks fine to me. So, merge it, I'd say.
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
2 participants
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.
On some Linux distributions, boost::filesystem::copy_file emits a
fstatfssyscall to query the filesystem metadata to determine if it can usecopy_file_rangeor if it needs to fall back to a read/write loop. Denying this syscall does not cause any functional issues, as the fallback logic is also used in case of EACCES, but it prevents the use ofcopy_file_rangewhich can lead to significant performance improvements when copying large files. For more details see #10711 (comment).I've started a Pipeline for this here (is not publicly accessible) to test whether the interface is available on all our supported distros.
fixes #10711