Re: [GIT PULL] notification tree

[Alexey Zaytsev]

Hi, Eric.

Now that the interface seems to be more or less set, could you please
document the new syscalls?
The last design document I could find is from 2009, and there seem to
be some updates.

On Sat, Oct 30, 2010 at 22:43, Eric Paris <eparis@xxxxxxxxxx> wrote:
> The notification tree has patches to address a number of fanotify
> complaints from last cycle. ÂThe most important being the (ABI
> compatible) addition of 'classes' which will allow things like
> hierarchical storage managers to receive events before scanners or
> indexers. ÂIt also includes default limits on the amount of memory an
> fanotify listener can consume and other minor changes. ÂAn updated
> example program which makes use of most all of the fanotify feature set
> can be found at
>
> http://git.infradead.org/users/eparis/fanotify-example.git
>
> ---
>
> The following changes since commit 2d10d8737ccdba752d60106abbc6ed4f37404923:
>
> ÂMerge branches 'x86-fixes-for-linus' and 'x86-uv-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip (2010-10-29 18:58:00 -0700)
>
> are available in the git repository at:
>
> Âgit://git.infradead.org/users/eparis/notify.git for-linus
>
> Andrew Morton (1):
> Â Â Âfs/notify/fanotify/fanotify_user.c: fix warnings
>
> Eric Paris (17):
> Â Â Âfanotify: allow fanotify to be built
> Â Â Âfsnotify: implement ordering between notifiers
> Â Â Âfanotify: implement fanotify listener ordering
> Â Â Âfanotify: use __aligned_u64 in fanotify userspace metadata
> Â Â Âfsnotify: correctly handle return codes from listeners
> Â Â Âfsnotify: call fsnotify_parent in perm events
> Â Â Âfanotify: allow userspace to flush all marks
> Â Â Âfanotify: ignore fanotify ignore marks if open writers
> Â Â Âfsnotify: implement a default maximum queue depth
> Â Â Âfanotify: allow userspace to override max queue depth
> Â Â Âfanotify: limit the number of marks in a single fanotify group
> Â Â Âfanotify: allow userspace to override max marks
> Â Â Âfanotify: limit number of listeners per user
> Â Â Âfanotify: do not send events for irregular files
> Â Â Âfsnotify: rename FS_IN_ISDIR to FS_ISDIR
> Â Â Âfanotify: ignore events on directories unless specifically requested
> Â Â Âfanotify: do not recalculate the mask if the ignored mask changed
>
> Lino Sanfilippo (2):
> Â Â Âmake fanotify_read() restartable across signals
> Â Â ÂEnsure FMODE_NONOTIFY is not set by userspace
>
> Richard Kennedy (1):
> Â Â Âfsnotify: remove alignment padding from fsnotify_mark on 64 bit builds
>
> Stefan Hajnoczi (1):
> Â Â Âfanotify: Fix FAN_CLOSE comments
>
> Âfs/notify/Kconfig         Â|  Â2 +-
> Âfs/notify/fanotify/fanotify.c   Â|  27 ++++++++--
> Âfs/notify/fanotify/fanotify_user.c | Â 98 +++++++++++++++++++++++++++++++++---
> Âfs/notify/fsnotify.c        |  35 ++++++++-----
> Âfs/notify/inode_mark.c       |  Â9 +++-
> Âfs/notify/inotify/inotify_user.c  |  Â2 +-
> Âfs/notify/vfsmount_mark.c     Â|  Â6 ++-
> Âinclude/linux/Kbuild        |  Â1 +
> Âinclude/linux/fanotify.h      |  36 ++++++++++---
> Âinclude/linux/fsnotify.h      |  38 ++++++++------
> Âinclude/linux/fsnotify_backend.h  |  26 +++++++--
> Âinclude/linux/sched.h       Â|  Â3 +
> Â12 files changed, 219 insertions(+), 64 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/
>
--
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/