mirror of
https://github.com/opnsense/src.git
synced 2026-03-02 05:13:58 -05:00
3227325366
* We never send FUSE_LOOKUP for the root inode, since its inode number is hard-coded to 1. Therefore, we should not send FUSE_FORGET for it, lest the server see its lookup count fall below 0. * During VOP_RECLAIM, if we are reclaiming the root inode, we must clear the file system's vroot pointer. Otherwise it will be left pointing at a reclaimed vnode, which will cause future VOP_LOOKUP operations to fail. Previously we only cleared that pointer during VFS_UMOUNT. I don't know of any real-world way to trigger this bug. MFC after: 2 weeks Reviewed by: pfg Differential Revision: https://reviews.freebsd.org/D34753 |
||
|---|---|---|
| .. | ||
| fuse.h | ||
| fuse_device.c | ||
| fuse_file.c | ||
| fuse_file.h | ||
| fuse_internal.c | ||
| fuse_internal.h | ||
| fuse_io.c | ||
| fuse_io.h | ||
| fuse_ipc.c | ||
| fuse_ipc.h | ||
| fuse_kernel.h | ||
| fuse_main.c | ||
| fuse_node.c | ||
| fuse_node.h | ||
| fuse_vfsops.c | ||
| fuse_vnops.c | ||