b0ecfb42d1
The FUSE protocol allows the client (kernel) to cache a file's size, if the server (userspace daemon) allows it. A well-behaved daemon obviously should not change a file's size while a client has it cached. But a buggy daemon might. If the kernel ever detects that that has happened, then it should invalidate the entire cache for that file. Previously, we would not only cache stale data, but in the case of a file extension while we had the size cached, we accidentally extended the cache with zeros. PR: 244178 Reported by: Ben RUBSON <ben.rubson@gmx.com> Reviewed by: cem MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D24012 |
||
|---|---|---|
| .. | ||
| 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 | ||