OS X: Getxattr sees bogus xattr names, sporadically

[tv42]

Observing the client side syscall:

$ sudo dtrace -n 'syscall::getxattr:entry { printf("%s %s %s",execname,copyinstr(arg0),copyinstr(arg1)); }'
  1    609                   getxattr:entry fs.test /var/folders/66/_jq2zs9d1pg929b5tdq_j0tw0000gn/T/fusetest787553602/child not-there

The above was observed while running

$ ./fs.test -test.run=TestGetxattr -fuse.debug -test.v

but the FUSE mount saw

fuse.GetxattrRequest{Header:fuse.Header{Conn:(*fuse.Conn)(0x20839c540), ID:0x6, Node:0x2, Uid:0x1f5, Gid:0x14, Pid:0xccb8}, Size:0x2000, Name:"\x10%9\b\x02", Position:0x0}

I also captured the raw data, and the read from kernel is

">\x00\x00\x00\x16\x00\x00\x00\x06\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\xf5\x01\x00\x00\x14\x00\x00\x00\xb8\xcc\x00\x00\x00\x00\x00\x00\x00 \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x10%9\b\x02\x00"

which seems to pinpoint the corruption to happening inside the kernel. Reproduced with osxfuse 2.7.5 and 2.7.0.

[tv42]

Heads up: the future of macOS support is in danger. If you care about FUSE on macOS, please encourage talented developers to pick up maintenance of the open source project. See #224

[tv42]

macOS support has been removed. If somebody wants to pick up maintaining an open source macOS FUSE, or wants to fund supporting the proprietary continuation of OSXFUSE, please get in touch.
#224