summaryrefslogtreecommitdiff
path: root/fs/ramfs
diff options
context:
space:
mode:
authorJohn McCutchan <ttb@tentacle.dhs.org>2005-08-08 13:52:16 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2005-08-08 11:53:47 -0700
commit7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a (patch)
treeffd77cfbf621a990052c1277d8a18451b9363dda /fs/ramfs
parent1963c907b21e140082d081b1c8f8c2154593c7d7 (diff)
downloadlinux-3.10-7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a.tar.gz
linux-3.10-7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a.tar.bz2
linux-3.10-7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a.zip
[PATCH] fsnotify_name/inoderemove
The patch below unhooks fsnotify from vfs_unlink & vfs_rmdir. It introduces two new fsnotify calls, that are hooked in at the dcache level. This not only more closely matches how the VFS layer works, it also avoids the problem with locking and inode lifetimes. The two functions are - fsnotify_nameremove -- called when a directory entry is going away. It notifies the PARENT of the deletion. This is called from d_delete(). - inoderemove -- called when the files inode itself is going away. It notifies the inode that is being deleted. This is called from dentry_iput(). Signed-off-by: John McCutchan <ttb@tentacle.dhs.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/ramfs')
0 files changed, 0 insertions, 0 deletions