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 changes for v4.20-rc1
Date: Mon, 29 Oct 2018 11:35:29 +0100	[thread overview]
Message-ID: <20181029103529.GC5988@quack2.suse.cz> (raw)

  Hello Linus,

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_v4.20-rc1

to get Amir's patches to implement superblock fanotify watches, Xiaoming's
patch to enable reporting of thread IDs in fanotify events instead of TGIDs
(sadly the patch got mis-attributed to Amir and I've noticed only now), and
a fix of possible oops on umount caused by fsnotify infrastructure.

Top of the tree is ee4af50ca94f. The full shortlog is:

Amir Goldstein (12):
      fsnotify: add super block object type
      fsnotify: send path type events to group with super block marks
      fanotify: add API to attach/detach super block mark
      fanotify: store fanotify_init() flags in group's fanotify_data
      fanotify: fix collision of internal and uapi mark flags
      fsnotify: generalize handling of extra event flags
      fanotify: simplify handling of FAN_ONDIR
      fanotify: deprecate uapi FAN_ALL_* constants
      fsnotify: convert runtime BUG_ON() to BUILD_BUG_ON()
      fanotify: add BUILD_BUG_ON() to count the bits of fanotify constants
      fanotify: support reporting thread id instead of process id
      fs: group frequently accessed fields of struct super_block together

Jan Kara (1):
      fsnotify: Fix busy inodes during unmount

The diffstat is

 fs/notify/fanotify/fanotify.c      |  17 +++---
 fs/notify/fanotify/fanotify.h      |   4 +-
 fs/notify/fanotify/fanotify_user.c | 103 +++++++++++++++++++++----------------
 fs/notify/fdinfo.c                 |  29 +++--------
 fs/notify/fsnotify.c               |  42 +++++++++------
 fs/notify/fsnotify.h               |  11 ++++
 fs/notify/inotify/inotify_user.c   |   2 +-
 fs/notify/mark.c                   |  43 +++++++++++++---
 fs/super.c                         |   2 +-
 include/linux/fanotify.h           |  59 ++++++++++++++++++++-
 include/linux/fs.h                 |  22 ++++++--
 include/linux/fsnotify_backend.h   |  30 ++++++++---
 include/uapi/linux/fanotify.h      |  25 ++++++---
 13 files changed, 267 insertions(+), 122 deletions(-)

							Thanks
								Honza

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

             reply	other threads:[~2018-10-29 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 10:35 Jan Kara [this message]
2018-10-29 16:21 ` [GIT PULL] fsnotify changes for v4.20-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=20181029103529.GC5988@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).