5403f2c163
Every FUSE operation has a unique value in its header. As the name implies, these values are supposed to be unique among all outstanding operations. And since FUSE_INTERRUPT is asynchronous and racy, it is desirable that the unique values be unique among all operations that are "close in time". Ensure that they are actually unique by incrementing them whenever we reuse a fuse_dispatcher object, for example during fsync, write, and listextattr. PR: 244686 MFC after: 2 weeks Reviewed by: pfg Differential Revision: https://reviews.freebsd.org/D30810 |
||
|---|---|---|
| .. | ||
| 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 | ||
| fuse.h | ||