search

macos-fuse-t / fuse-t

Other
934 stars 7 forks source link

The key name becomes empty after successive xattr writes #74

Open ggtakec opened 3 weeks ago

ggtakec commented 3 weeks ago

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 https://github.com/s3fs-fuse/s3fs-fuse/issues/2585.

Thanks in advance for your help.

macos-fuse-t commented 3 weeks ago

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