linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
	Matthew Bobrowski <mbobrowski@mbobrowski.org>,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v5 00/17] fanotify: add support for more event types
Date: Thu, 7 Feb 2019 17:26:04 +0100	[thread overview]
Message-ID: <20190207162604.GK3597@quack2.suse.cz> (raw)
In-Reply-To: <20190110170444.30616-1-amir73il@gmail.com>

Hello,

On Thu 10-01-19 19:04:27, Amir Goldstein wrote:
> This is the 5th revision of patch series to add support for filesystem
> change monitoring to fanotify.
> 
> The complete work is available on fanotify_dirent-v5 branch [1] on github.
> 
> LTP tests by Matthew Bobrowski for FAN_REPORT_FID are available on
> my LTP branch fanotify_fid [2]. A WIP test for dirent events is
> available on my LTP branch fanotify_dirent [3].
> Matthew Bobrowski is working on a proper test for dirent events and on
> man pages for both FAN_REPORT_FID and dirent events (Thanks!).
> 
> The combined functionality of FAN_MARK_FILESYSTEM, FAN_REPORT_FID and
> dirent modification events is demonstrated with a prototype of global
> filesystem monitor based on inotify-tools [4].

OK, I've finally got to reading all the patches and pushing them to my tree
with some small changes. The result is in 'fsnotify' branch in my tree. All
LTP tests (including the new ones) passed so if 0-day does not barf, I'll
push the branch to for_next tomorrow. Thanks for your work!

								Honza

> 
> Thanks,
> Amir.
> 
> Changes since v4:
> - Rebase on v5.0-rc1
> - Address style review comments on v4
> - info_len includes padding to info_hdr alignment
> - handle caching of fsid correctly when inotify marks on object exist
> - Report dirent events on subdirs only with FAN_ONDIR
> - Report XXX_SELF events on directories only with FAN_ONDIR
> - Do not merge dirent events on subdirs with dirent events on non subdirs
> 
> [1] https://github.com/amir73il/linux/commits/fanotify_dirent-v5
> [2] https://github.com/amir73il/ltp/commits/fanotify_fid
> [3] https://github.com/amir73il/ltp/commits/fanotify_dirent
> [4] https://github.com/amir73il/inotify-tools/commits/fanotify_dirent
> 
> Amir Goldstein (17):
>   fsnotify: annotate directory entry modification events
>   fsnotify: remove dirent events from FS_EVENTS_POSS_ON_CHILD mask
>   fsnotify: send all event types to super block marks
>   fsnotify: move mask out of struct fsnotify_event
>   fanotify: rename struct fanotify_{,perm_}event_info
>   fanotify: open code fill_event_metadata()
>   fanotify: encode file identifier for FAN_REPORT_FID
>   fanotify: copy event fid info to user
>   fanotify: enable FAN_REPORT_FID init flag
>   fanotify: cache fsid in fsnotify_mark_connector
>   vfs: add vfs_get_fsid() helper
>   fanotify: use vfs_get_fsid() helper instead of vfs_statfs()
>   fsnotify: report FS_ISDIR flag with MOVE_SELF and DELETE_SELF events
>   fanotify: check FS_ISDIR flag instead of d_is_dir()
>   fanotify: support events with data type FSNOTIFY_EVENT_INODE
>   fanotify: add support for create/attrib/move/delete events
>   fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID
> 
>  fs/notify/fanotify/fanotify.c        | 229 +++++++++++++++++----
>  fs/notify/fanotify/fanotify.h        | 105 ++++++++--
>  fs/notify/fanotify/fanotify_user.c   | 288 +++++++++++++++++++--------
>  fs/notify/fsnotify.c                 |  15 +-
>  fs/notify/inotify/inotify.h          |   1 +
>  fs/notify/inotify/inotify_fsnotify.c |  18 +-
>  fs/notify/inotify/inotify_user.c     |   5 +-
>  fs/notify/mark.c                     |  47 ++++-
>  fs/notify/notification.c             |  22 +-
>  fs/statfs.c                          |  14 ++
>  include/linux/fanotify.h             |  26 ++-
>  include/linux/fsnotify.h             |  94 +++++++--
>  include/linux/fsnotify_backend.h     |  70 ++++---
>  include/linux/statfs.h               |   3 +
>  include/uapi/linux/fanotify.h        |  29 +++
>  15 files changed, 753 insertions(+), 213 deletions(-)
> 
> -- 
> 2.17.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      parent reply	other threads:[~2019-02-07 16:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 17:04 [PATCH v5 00/17] fanotify: add support for more event types Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 01/17] fsnotify: annotate directory entry modification events Amir Goldstein
2019-02-06 14:14   ` Jan Kara
2019-01-10 17:04 ` [PATCH v5 02/17] fsnotify: remove dirent events from FS_EVENTS_POSS_ON_CHILD mask Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 03/17] fsnotify: send all event types to super block marks Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 04/17] fsnotify: move mask out of struct fsnotify_event Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 05/17] fanotify: rename struct fanotify_{,perm_}event_info Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 06/17] fanotify: open code fill_event_metadata() Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 07/17] fanotify: encode file identifier for FAN_REPORT_FID Amir Goldstein
2019-01-11  8:10   ` kbuild test robot
2019-01-11  8:37     ` Amir Goldstein
2019-01-18 18:39       ` Paul Burton
2019-01-10 17:04 ` [PATCH v5 08/17] fanotify: copy event fid info to user Amir Goldstein
2019-02-06 17:41   ` Jan Kara
2019-01-10 17:04 ` [PATCH v5 09/17] fanotify: enable FAN_REPORT_FID init flag Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 10/17] fanotify: cache fsid in fsnotify_mark_connector Amir Goldstein
2019-01-11  3:13   ` kbuild test robot
2019-01-14  7:30   ` Dan Carpenter
2019-01-14  7:30     ` Dan Carpenter
2019-01-14  9:17     ` Amir Goldstein
2019-02-07 14:48   ` Jan Kara
2019-02-07 16:31     ` Amir Goldstein
2019-02-08 10:15       ` Jan Kara
2019-01-10 17:04 ` [PATCH v5 11/17] vfs: add vfs_get_fsid() helper Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 12/17] fanotify: use vfs_get_fsid() helper instead of vfs_statfs() Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 13/17] fsnotify: report FS_ISDIR flag with MOVE_SELF and DELETE_SELF events Amir Goldstein
2019-02-07 14:57   ` Jan Kara
2019-01-10 17:04 ` [PATCH v5 14/17] fanotify: check FS_ISDIR flag instead of d_is_dir() Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 15/17] fanotify: support events with data type FSNOTIFY_EVENT_INODE Amir Goldstein
2019-02-07 15:18   ` Jan Kara
2019-02-07 16:10     ` Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 16/17] fanotify: add support for create/attrib/move/delete events Amir Goldstein
2019-01-10 17:04 ` [PATCH v5 17/17] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID Amir Goldstein
2019-02-07 16:26 ` 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=20190207162604.GK3597@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=amir73il@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mbobrowski@mbobrowski.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).