7430017b99
fuse_vnop_bmap needs to know the file's size in order to calculate the optimum amount of readahead. If the file's size is unknown, it must ask the FUSE server. But if the file's data was previously cached and the server reports that its size has shrunk, fusefs must invalidate the cached data. That's not possible during VOP_BMAP because the buffer object is already locked. Fix the panic by not querying the FUSE server for the file's size during VOP_BMAP if we don't need it. That's also a a slight performance optimization. PR: 256937 Reported by: Agata <chogata@moosefs.pro> Tested by: Agata <chogata@moosefs.pro> MFC after: 2 weeks |
||
|---|---|---|
| .. | ||
| 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 | ||