lkml.org 
[lkml]   [2010]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [GIT PULL] notification tree
From
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@redhat.com> 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@vger.kernel.org
> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2010-10-31 15:01    [W:0.048 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site