Status of FUSE in FreeBSD kernel

[Conrad Meyer]

Hi Nikolaus,

These questions are probably best answered by reading the source.

I grepped the FreeBSD tree for FUSE_NOTIFY_INVAL_INODE and did not see
it.  Looking around, I don't think we have any of the libfuse notify
support.

As far as mknod/mkfifo, that should work.  EINVAL can come from bogus
dev value for a CHR/BLK mknod or an unrecognized mode type.

Best,
Conrad


On Fri, Aug 11, 2017 at 11:58 AM, Nikolaus Rath <Nikolaus at rath.org> wrote:
> On Aug 11 2017, Nikolaus Rath <Nikolaus at rath.org> wrote:
>> Is there some resource that gives an overview of the features supported
>> by the FUSE kernel module in FreeBSD?
>>
>> For example, I am wondering if the EINVAL error that I'm getting when
>> sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error
>> on my side, or because the FreeBSD kernel just doesn't support it.
>>
>> I expect to encounter the same question for a number of other functions,
>> e.g. the other FUSE_NOTIFY_* requests.
>
> Another example: calling 'mknod' or 'mkfifo' on a FUSE mountpoint
> doesn't seem to make it through to the filesystem, the kernel returns
> -EINVAL instead.
>
> Is that a problem with the filesystem, or not supported by the kernel?
>
> Thanks!
> -Nikolaus