fs: workaround quirkly overlayfs listxattr() #43
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.
We use listxattr() with an empty buffer (as documented in the manpage) to query the size of the xattrs that are present. Unfortunately, this "empty buffer" case hits a shortcut in the xattr code in overlayfs which happens before the overlayfs-internal xattrs are filtered out.
Once we perform the read "for real" we hit the filter path and the returned xattrs are smaller than we were expecting.
Let's deal with that by accepting a smaller return value from the second call and truncating the buffer to that length.
Thanks to Shawn Wang [email protected] for the report.
Closes #41