summaryrefslogtreecommitdiffstats
path: root/fs/bad_inode.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2016-10-07 16:56:55 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2016-10-07 18:46:26 -0700
commit073f65522aeb23e46fc8a809d69513132d3acc81 (patch)
tree628b7586e7f70ba13b6ccff48efbbec571fde8b7 /fs/bad_inode.c
parentc21dbe20f606219fe54faf555b7bc5565487c58f (diff)
downloadlinux-073f65522aeb23e46fc8a809d69513132d3acc81.tar.gz
linux-073f65522aeb23e46fc8a809d69513132d3acc81.tar.bz2
linux-073f65522aeb23e46fc8a809d69513132d3acc81.zip
fanotify: use notification_lock instead of access_lock
Fanotify code has its own lock (access_lock) to protect a list of events waiting for a response from userspace. However this is somewhat awkward as the same list_head in the event is protected by notification_lock if it is part of the notification queue and by access_lock if it is part of the fanotify private queue which makes it difficult for any reliable checks in the generic code. So make fanotify use the same lock - notification_lock - for protecting its private event list. Link: http://lkml.kernel.org/r/1473797711-14111-6-git-send-email-jack@suse.cz Signed-off-by: Jan Kara <jack@suse.cz> Reviewed-by: Lino Sanfilippo <LinoSanfilippo@gmx.de> Cc: Miklos Szeredi <mszeredi@redhat.com> Cc: Eric Paris <eparis@redhat.com> Cc: Al Viro <viro@ZenIV.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/bad_inode.c')
0 files changed, 0 insertions, 0 deletions