alistair23-linux/fs/notify
Eric Paris 75fe2b2639 inotify: do not leak inode marks in inotify_add_watch
inotify_add_watch had a couple of problems.  The biggest being that if
inotify_add_watch was called on the same inode twice (to update or change the
event mask) a refence was taken on the original inode mark by
fsnotify_find_mark_entry but was not being dropped at the end of the
inotify_add_watch call.  Thus if inotify_rm_watch was called although the mark
was removed from the inode, the refcnt wouldn't hit zero and we would leak
memory.

Reported-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Eric Paris <eparis@redhat.com>
2009-07-21 15:26:26 -04:00
..
dnotify fsnotify: allow groups to set freeing_mark to null 2009-06-11 14:57:55 -04:00
inotify inotify: do not leak inode marks in inotify_add_watch 2009-07-21 15:26:26 -04:00
fsnotify.c inotify/dnotify: should_send_event shouldn't match on FS_EVENT_ON_CHILD 2009-06-11 14:57:54 -04:00
fsnotify.h fsnotify: generic notification queue and waitq 2009-06-11 14:57:53 -04:00
group.c fsnotify: generic notification queue and waitq 2009-06-11 14:57:53 -04:00
inode_mark.c fsnotify: allow groups to set freeing_mark to null 2009-06-11 14:57:55 -04:00
Kconfig fsnotify: unified filesystem notification backend 2009-06-11 14:57:52 -04:00
Makefile fsnotify: add marks to inodes so groups can interpret how to handle those inodes 2009-06-11 14:57:53 -04:00
notification.c fsnotify: allow groups to add private data to events 2009-06-11 14:57:54 -04:00