[GIT PULL] notification fixes
From: Eric Paris
Date: Fri Aug 27 2010 - 22:10:25 EST
Mostly bug fixes found when testing the fanotify vfsmounts.
The most serious bug (and only one affecting inotify and dnotify rather
than requiring fanotify to break something) was actually fixed
accidentally in "fsnotify: fix ignored mask handling between inode and
vfsmount marks". It was possible for inotify to get events it didn't
request or even events with a 0 mask.
The only other interesting note is that "fanotify: resize pid and
reorder structure" will require users to rebuild any fanotify listeners.
It's an ABI change, not an API change, which should help us improve
performance in the future on strict alignment platforms (without
breaking ABI)
-Eric
The following changes since commit d4348c678977c7093438bbbf2067c49396ae941b:
Merge branch 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip (2010-08-25 10:50:07 -0700)
are available in the git repository at:
git://git.infradead.org/users/eparis/notify.git for-linus
Andreas Gruenbacher (1):
fanotify: Return EPERM when a process is not privileged
Eric Paris (7):
fanotify: do not dereference inode_mark when it is unset
fsnotify: reset used_inode and used_vfsmount on each pass
fanotify: add MAINTAINERS entry
fsnotify: fix ignored mask handling between inode and vfsmount marks
fanotify: flush outstanding perm requests on group destroy
fsnotify: fix list walk order
fsnotify: drop two useless bools in the fnsotify main loop
Tvrtko Ursulin (2):
fanotify: drop duplicate pr_debug statement
fanotify: resize pid and reorder structure
MAINTAINERS | 6 +++
fs/notify/fanotify/fanotify.c | 3 --
fs/notify/fanotify/fanotify_user.c | 29 +++++++++++++++-
fs/notify/fsnotify.c | 68 +++++++++++++++++++-----------------
include/linux/fanotify.h | 13 ++-----
include/linux/fsnotify_backend.h | 1 +
6 files changed, 74 insertions(+), 46 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/