linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Fsnotify patches for v5.7-rc1
Date: Mon, 6 Apr 2020 13:44:31 +0200	[thread overview]
Message-ID: <20200406114431.GF1143@quack2.suse.cz> (raw)

  Hello Linus,

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify_for_v5.7-rc1

This pull contains patches implementing fanotify FAN_DIR_MODIFY event. This
event reports name in a directory under which change happened and together
with directory filehandle and fstatat() allows reliable and efficient
implementation of directory synchronization.

Top of the tree is 6def1a1d2d58. The full shortlog is:

Amir Goldstein (12):
      fsnotify: tidy up FS_ and FAN_ constants
      fsnotify: factor helpers fsnotify_dentry() and fsnotify_file()
      fsnotify: funnel all dirent events through fsnotify_name()
      fsnotify: use helpers to access data by data_type
      fsnotify: simplify arguments passing to fsnotify_parent()
      fsnotify: replace inode pointer with an object id
      fanotify: merge duplicate events on parent and child
      fanotify: fix merging marks masks with FAN_ONDIR
      fanotify: send FAN_DIR_MODIFY event flavor with dir inode and name
      fanotify: prepare to report both parent and child fid's
      fanotify: record name info for FAN_DIR_MODIFY event
      fanotify: report name info for FAN_DIR_MODIFY event

Jan Kara (4):
      fanotify: Simplify create_fd()
      fanotify: Store fanotify handles differently
      fanotify: divorce fanotify_path_event and fanotify_fid_event
      fanotify: Drop fanotify_event_has_fid()

Nathan Chancellor (1):
      fanotify: Fix the checks in fanotify_fsid_equal

The diffstat is

 fs/notify/fanotify/fanotify.c        | 302 ++++++++++++++++++++++++++---------
 fs/notify/fanotify/fanotify.h        | 189 +++++++++++++++-------
 fs/notify/fanotify/fanotify_user.c   | 220 ++++++++++++++++---------
 fs/notify/fsnotify.c                 |  22 +--
 fs/notify/inotify/inotify_fsnotify.c |  12 +-
 fs/notify/inotify/inotify_user.c     |   2 +-
 include/linux/fanotify.h             |   3 +-
 include/linux/fsnotify.h             | 138 +++++++---------
 include/linux/fsnotify_backend.h     |  70 +++++---
 include/uapi/linux/fanotify.h        |  13 +-
 kernel/audit_fsnotify.c              |  13 +-
 kernel/audit_watch.c                 |  16 +-
 12 files changed, 637 insertions(+), 363 deletions(-)

							Thanks
								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

             reply	other threads:[~2020-04-06 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 11:44 Jan Kara [this message]
2020-04-06 16:45 ` [GIT PULL] Fsnotify patches for v5.7-rc1 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200406114431.GF1143@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).