Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The key name becomes empty after successive xattr writes #74

Open
ggtakec opened this issue Nov 2, 2024 · 1 comment
Open

The key name becomes empty after successive xattr writes #74

ggtakec opened this issue Nov 2, 2024 · 1 comment

Comments

@ggtakec
Copy link

ggtakec commented Nov 2, 2024

Hi, macos-fuse-t developer

We are reporting an unknown behavior of macos-fuse-t that was detected during the s3fs-fuse inspection.

Our xattr write/read test is performed as follows:

set_xattr key1 value0 <file>        (1)
get_xattr key1 <file>               (2)
set_xattr key1 value1 <file>        (3)
get_xattr key1 <file>               (4)

When executing command (3), there seems to be a problem with the argument to the hook call of setxattrcalled by FUSE.
The xattr key name passed to the setxattr hook is empty(empty string: "").
Also, the file open for the getxattr call in command (4) immediately following and the open for setxattr are executed simultaneously.

Is this behavior correct?

For more details, please refer to s3fs-fuse/s3fs-fuse#2585.

Thanks in advance for your help.

@macos-fuse-t
Copy link
Owner

I will need to look into it. NFS to FUSE translation with regards to xattrs is a bit finicky.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants