android_kernel_xiaomi_sm8350/fs/notify/inotify
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
..
inotify_fsnotify.c inotify: inotify_destroy_mark_entry could get called twice 2009-06-19 12:42:48 -04:00
inotify_user.c inotify: do not leak inode marks in inotify_add_watch 2009-07-21 15:26:26 -04:00
inotify.c fsnotify: unified filesystem notification backend 2009-06-11 14:57:52 -04:00
inotify.h inotify: inotify_destroy_mark_entry could get called twice 2009-06-19 12:42:48 -04:00
Kconfig inotify: reimplement inotify using fsnotify 2009-06-11 14:57:54 -04:00
Makefile inotify: reimplement inotify using fsnotify 2009-06-11 14:57:54 -04:00