Han-Wen Nienhuys

you can pick 'reviewer' option which shouldn't require handing out push access.

There are probably not that many difficulties. IIRC, you basically have a write out a binary blob, depending on the incoming IOCTL requested.

``` {"level":"debug","msg":"2021/11/11 02:20:52 rx 254: IOCTL n2 *fuse._IoctlIn: \u0026{{72 39 254 2 {{0 0} 5482} 0} 2 16 2148034049 0 0 4} ","time":"2021-11-11T02:20:52.475822959Z"} {"level":"debug","msg":"2021/11/11 02:20:52 tx 254: 38=function not implemented","time":"2021-11-11T02:20:52.475839601Z"}...

could you push to Gerrithub? See https://github.com/hanwen/go-fuse/blob/3ab5d95a30ae25019bf030a2bab076dba61c27da/CONTRIBUTING would it be possilbe to add a test?

what does a libfuse FS do in this case? Would it not also fail?

note to self: ioctl constants interpreted here: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux/+/136057256686de39cc3a07c2e39ef6bc43003ff6/fs/ioctl.c#839 and https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux/+/136057256686de39cc3a07c2e39ef6bc43003ff6/fs/ioctl.c#845 implementation https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux/+/136057256686de39cc3a07c2e39ef6bc43003ff6/fs/ioctl.c#739 and https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux/+/136057256686de39cc3a07c2e39ef6bc43003ff6/fs/ioctl.c#708 there is a ENOIOCTLCMD errno value, https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux/+/136057256686de39cc3a07c2e39ef6bc43003ff6/include/linux/errno.h#17 which should be used to signal nonexistent ioctls ?

I have this script to clean up my connections: ``` $ cat ~/bin/kill-all-fuse.sh #!/bin/sh set -eux cd /sys/fs/fuse/connections for f in *; do echo $f echo hoi > $f/abort done...

have a look at opcode.go, https://github.com/hanwen/go-fuse/blob/02b38384c28d568e5f9da00924007fd101d56099/fuse/opcode.go You should define the right opcode, and set up handlers for it. Then you wire this through RawFileSystem (see https://github.com/hanwen/go-fuse/blob/02b38384c28d568e5f9da00924007fd101d56099/fuse/api.go) and from there to...

why do you want to implement the '.' and '..' entries?

I think it would be easy to make '.' and '..' work correctly. '..' is the parent, so it should be possible to lookup the parent's ino number and populate...