add ENOATTR & E2BIG
#34
Merged
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
infeo
approved these changes
Sep 5, 2023
There was a problem hiding this comment.
Interesting curiosity.
As a side-note, on the netbsd kernel mailing list exists a converstion about ENODATA vs ENOATTR: https://tech-kern.netbsd.narkive.com/JcRAFrPC/enoattr-vs-enodata
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.
Add two more error codes that may be relevant to correctly implement xattr.
ENOATTRis macOS-specific (BSD-specific, to be exact). On Linux,ENODATAis commonly aliased byENOATTR, which is why this impl does the same. It is expected to be returned instead ofENODATAwhen agetxattrcan not find the given attr.E2BIGis expected to be returned bysetxattr, when the given value is... too big.