When a watch is added on a super block's root inode with
the FS_EVENT_ON_SB flag, the watched inode is intended
to report events on all inodes on the same super block.
Signed-off-by: Amir Goldstein
---
fs/notify/fsnotify.c | 2 +-
include/linux/fsnotify_backend.h | 19 ++
fsnotify_mark_srcu[1] protects reads of the first half of inode/vfsmount
mark lists, which consist of the high priority (>0) marks, whose masks
may contain permission events.
fsnotify_mark_srcu[0] protects reads of the second half of inode/vfsmount
mark lists, which consist of the low priority (0)
* David Woodhouse ([EMAIL PROTECTED]) wrote:
> What would make sense, perhaps, would be to actually merge those hooks;
> not just a cosmetic amalgamation of the calling sites. Currently, each
> of inotify and the audit code does its own filtering when its hooks are
> triggered, and then acts upon t
On Mon, 2005-07-11 at 13:52 +0100, David Woodhouse wrote:
> To be honest, I don't really see that this is in any way better than
> what we had before. Yes, two different pieces of code actually use hooks
> in similar places in the VFS code. But this 'infrastructure' just to
> share those hooks is
On Fri, 2005-07-08 at 18:26 -0700, Chris Wright wrote:
> Add fsnotify as infrastructure for various fs notifcation schemes.
> Move dnotify to fsnotify.
- inode_dir_notify(dir, DN_CREATE);
+ fsnotify_create(dir, new_dentry->d_name.name);
+ * We don't compile any of
Add fsnotify as infrastructure for various fs notifcation schemes.
Move dnotify to fsnotify.
fs/attr.c| 33 +
fs/compat.c | 12 +++-
fs/file_table.c |3 +
fs/namei.c | 30 ++-
fs/nfsd/vfs.c|6 +-
f
6 matches
Mail list logo
