From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
Marko Rauhamaa <marko.rauhamaa@f-secure.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] fanotify super block marks
Date: Mon, 3 Sep 2018 15:20:51 +0200 [thread overview]
Message-ID: <20180903132051.GI10027@quack2.suse.cz> (raw)
In-Reply-To: <20180901074113.32296-1-amir73il@gmail.com>
Hi Amir!
On Sat 01-09-18 10:41:10, Amir Goldstein wrote:
> The following patches implement the new mark type FAN_MARK_FILESYSTEM
> to enable monitoring of filesystem events on all filesystem objects
> regardless of the mount where event was generated.
>
> These patches are available on my github [1] along with LTP tests [2]
> and man-pages update [3].
Thanks for the patches! I've queued them up to my tree for the next merge
window (will publish them as soon as LTP tests are finished). I've just
fixed a typo in comment in patch 3 and added comments into holes in flags
space in fanotify.h header.
Honza
> [1] https://github.com/amir73il/linux/commits/fanotify_sb
> [2] https://github.com/amir73il/ltp/commits/fanotify_sb
> [3] https://github.com/amir73il/man-pages/commits/fanotify_sb
>
> Changes since v3:
> - Rebase on top of ignore mask fix patch
> - Address "semantic" review comments on FAN_MARK_FILESYSTEM flag
>
> Changes since v2:
> - Rebased on top of merged cleanup patches
> - Show super block marks in fanotify_fdinfo()
> - Add man pages patch [3]
>
> Amir Goldstein (3):
> 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
>
> fs/notify/fanotify/fanotify_user.c | 37 ++++++++++++++++++++++++++----
> fs/notify/fdinfo.c | 5 ++++
> fs/notify/fsnotify.c | 32 +++++++++++++++++---------
> fs/notify/fsnotify.h | 11 +++++++++
> fs/notify/mark.c | 4 ++++
> fs/super.c | 2 +-
> include/linux/fs.h | 5 ++++
> include/linux/fsnotify_backend.h | 17 +++++++++++---
> include/uapi/linux/fanotify.h | 7 +++++-
> 9 files changed, 99 insertions(+), 21 deletions(-)
>
> --
> 2.17.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2018-09-03 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 7:41 [PATCH v4 0/3] fanotify super block marks Amir Goldstein
2018-09-01 7:41 ` [PATCH v4 1/3] fsnotify: add super block object type Amir Goldstein
2018-09-01 7:41 ` [PATCH v4 2/3] fsnotify: send path type events to group with super block marks Amir Goldstein
2018-09-01 7:41 ` [PATCH v4 3/3] fanotify: add API to attach/detach super block mark Amir Goldstein
2018-09-03 13:20 ` Jan Kara [this message]
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=20180903132051.GI10027@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marko.rauhamaa@f-secure.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.