Neuter fuse_vptofh() and fuse_fhtovp(). I implemented those functions
authornatano <natano@openbsd.org>
Mon, 15 Aug 2016 07:39:46 +0000 (07:39 +0000)
committernatano <natano@openbsd.org>
Mon, 15 Aug 2016 07:39:46 +0000 (07:39 +0000)
commit514c5354f8853d80251752aa2b39dc8d690f0ded
treec19feff662f36df41cf58a81eaf64abe378b34b8
parent33da7fa5ad9a5c736d992b64b8e65f949146a490
Neuter fuse_vptofh() and fuse_fhtovp(). I implemented those functions
under the assumption, that fuse_vget() has reasonable semantics, while
this is not the case. fusefs_vget() only functions correctly, if the
file in questions has recently been accessed and is still in the vnode
cache of the userspace daemon associated with the mount point.

As a matter of fact the fuse api doesn't feature a reasonable way to map
inode numbers to a handle at all (see struct fuse_operations).

ok guenther
sys/miscfs/fuse/fuse_vfsops.c