1
linux/fs/notify
Eric Paris 9dced01a09 fanotify: do not clone on merge unless needed
Currently if 2 events are going to be merged on the notication queue with
different masks the second event will be cloned and will replace the first
event.  However if this notification queue is the only place referencing
the event in question there is no reason not to just update the event in
place.  We can tell this if the event->refcnt == 1.  Since we hold a
reference for each queue this event is on we know that when refcnt == 1
this is the only queue.  The other concern is that it might be about to be
added to a new queue, but this can't be the case since fsnotify holds a
reference on the event until it is finished adding it to queues.

Signed-off-by: Eric Paris <eparis@redhat.com>
2010-07-28 09:58:55 -04:00
..
dnotify fsnotify: take inode->i_lock inside fsnotify_find_mark_entry() 2010-07-28 09:58:54 -04:00
fanotify fanotify: do not clone on merge unless needed 2010-07-28 09:58:55 -04:00
inotify fsnotify: take inode->i_lock inside fsnotify_find_mark_entry() 2010-07-28 09:58:54 -04:00
fsnotify.c fsnotify: kill FSNOTIFY_EVENT_FILE 2010-07-28 09:58:53 -04:00
fsnotify.h fsnotify: mount point listeners list and global mask 2010-07-28 09:58:52 -04:00
group.c fsnotify: rename mark_entry to just mark 2010-07-28 09:58:53 -04:00
inode_mark.c fsnotify: take inode->i_lock inside fsnotify_find_mark_entry() 2010-07-28 09:58:54 -04:00
Kconfig fanotify: fscking all notification system 2010-07-28 09:58:54 -04:00
Makefile fanotify: fscking all notification system 2010-07-28 09:58:54 -04:00
notification.c fsnotify: kill FSNOTIFY_EVENT_FILE 2010-07-28 09:58:53 -04:00