CismonX

Took a look at the corresponding source code of the [kernel](https://elixir.bootlin.com/linux/v6.8.9/source/fs/fuse/ioctl.c#L167) and [libfuse](https://github.com/libfuse/libfuse/blob/fuse-3.16.2/lib/fuse_lowlevel.c#L1816), it appears that the `void *arg` argument is the third argument passed to `ioctl()`, and `void *data`...

@asomers > any real-world fuse file systems that implement FUSE_IOCTL None that I'm aware of. However, one of my work-in-progress hobby projects (which is a pseudo filesystem for managing web...

Recently I came across two FUSE filesystems that implement `FUSE_IOCTL`. --- One of them is bindfs. When launched with the `-o enable-ioctl` option, it enables ioctl forwarding. However, it only...

Patch updated with the following changes: - [x] Update the copyright notice in the added test file. - [x] Add a `Signed-off-by:` line in all commit messages. - [x] Add...

@asomers Sorry if I'm being pushy, but it's been a while since the last update. Would you have time to continue reviewing this patch?

Just rebased HEAD without other changes. Fortunately the patch still works :)

@asomers I've refactored the tests as you suggested.

@asomers 15.0-ALPHA has been around for a while, and I'm wondering if this patch could still make it into 15. If there are anything else I need to do, please...

Take a look at FreeBSD's [`getcwd()`](https://github.com/freebsd/freebsd-src/blob/releng/14.1/lib/libc/gen/getcwd.c) implementation: 1. It first attempts to make a `__getcwd` system call, which fails with `ENOENT` (we will discuss about this later), and falls back...

More background on this patch: The `fuse_filehandle_get_dir()` function was introduced in commit f8d4af104b7d. This commit (unintentionally?) added an extra search for an `FEXEC` file handle in `fuse_vnop_readdir()`, which is not...