diff options
author | David Howells <dhowells@redhat.com> | 2012-12-20 21:52:36 +0000 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2012-12-20 22:06:08 +0000 |
commit | 9dc8d9bfe4415efb61a5e9390706b8a3bffef329 (patch) | |
tree | 2534486c442b7889a761d894f3bd4dd0403608ca /fs/nfs/inode.c | |
parent | a02de9608595c8ef649ef03ae735b0b45e3d4396 (diff) | |
download | op-kernel-dev-9dc8d9bfe4415efb61a5e9390706b8a3bffef329.zip op-kernel-dev-9dc8d9bfe4415efb61a5e9390706b8a3bffef329.tar.gz |
CacheFiles: Implement invalidation
Implement invalidation for CacheFiles. This is in two parts:
(1) Provide an invalidation method (which just truncates the backing file).
(2) Abort attempts to copy anything read from the backing file whilst
invalidation is in progress.
Question: CacheFiles uses truncation in a couple of places. It has been using
notify_change() rather than sys_truncate() or something similar. This means
it bypasses a bunch of checks and suchlike that it possibly should be making
(security, file locking, lease breaking, vfsmount write). Should it be using
vfs_truncate() as added by a preceding patch or should it use notify_write()
and assume that anyone poking around in the cache files on disk gets
everything they deserve?
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/nfs/inode.c')
0 files changed, 0 insertions, 0 deletions