public inbox for linux-fsdevel@vger.kernel.org
 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 changes for v4.21-rc1
Date: Thu, 20 Dec 2018 14:42:09 +0100	[thread overview]
Message-ID: <20181220134209.GA15045@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_v4.20-rc8

to get support for new FAN_OPEN_EXEC event and couple of cleanups around
fsnotify.

Top of the tree is 2aad26fa0a3d. The full shortlog is:

Eric Biggers (1):
      fsnotify/fdinfo: include fdinfo.h for inotify_show_fdinfo()

Kees Cook (1):
      fanotify: Make sure to check event_len when copying

Matthew Bobrowski (4):
      fanotify: return only user requested event types in event mask
      fanotify: introduce new event mask FAN_OPEN_EXEC
      fsnotify: refactor fsnotify_parent()/fsnotify() paired calls when event is on path
      fanotify: introduce new event mask FAN_OPEN_EXEC_PERM

Nikolay Borisov (1):
      fanotify: Use inode_is_open_for_write

The diffstat is

 fs/notify/fanotify/fanotify.c      | 32 ++++++++++++--------
 fs/notify/fanotify/fanotify_user.c | 12 ++++++--
 fs/notify/fdinfo.c                 |  1 +
 fs/notify/fsnotify.c               |  2 +-
 include/linux/fanotify.h           |  5 ++--
 include/linux/fsnotify.h           | 61 ++++++++++++++++++++++----------------
 include/linux/fsnotify_backend.h   | 11 +++++--
 include/uapi/linux/fanotify.h      |  2 ++
 8 files changed, 79 insertions(+), 47 deletions(-)

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

             reply	other threads:[~2018-12-20 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 13:42 Jan Kara [this message]
2018-12-28  1:00 ` [GIT PULL] Fsnotify changes for v4.21-rc1 Linus Torvalds

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=20181220134209.GA15045@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