From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 00/13] Preparing for fanotify super block marks
Date: Fri, 20 Apr 2018 16:10:48 -0700 [thread overview]
Message-ID: <1524265861-6316-1-git-send-email-amir73il@gmail.com> (raw)
Jan,
Per your request, here is the prep series for super block mark, with
all review comments addressed and rebased on your for_next branch.
For those interested in the super block marks work, here are the
patches [1] and ltp tests [2]. I hope we can iron out any remaining
concerns during LSF/MM.
Thanks,
Amir.
[1] https://github.com/amir73il/linux/commits/fanotify_sb
[2] https://github.com/amir73il/ltp/commits/fanotify_sb
Changes since v2:
- Some fix patches already merged
- Remove patches that implement super block mark
- Refernce abstract fsnotify_obj from connector
- Address Jan's review comments on type iteration helpers
- Better names for helpers and report_mask
Amir Goldstein (13):
fsnotify: use type id to identify connector object type
fsnotify: remove redundant arguments to handle_event()
fsnotify: introduce marks iteration helpers
fsnotify: generalize iteration of marks by object type
fsnotify: generalize send_to_group()
fanotify: generalize fanotify_should_send_event()
fsnotify: add fsnotify_add_inode_mark() wrappers
fsnotify: introduce prototype struct fsnotify_obj
fsnotify: pass fsnotify_obj instead of **connp argument
fsnotify: pass object and object type to fsnotify_add_mark()
fsnotify: add fsnotify_connector_inode() wrapper
fsnotify: let connector point to abstract fsnotify_obj
fanotify: factor out helpers to add/remove mark
fs/inode.c | 2 +-
fs/mount.h | 11 ++-
fs/notify/dnotify/dnotify.c | 16 ++--
fs/notify/fanotify/fanotify.c | 48 +++++------
fs/notify/fanotify/fanotify_user.c | 98 ++++++++-------------
fs/notify/fdinfo.c | 12 +--
fs/notify/fsnotify.c | 160 ++++++++++++++++++++---------------
fs/notify/fsnotify.h | 14 +--
fs/notify/group.c | 2 +-
fs/notify/inotify/inotify.h | 2 -
fs/notify/inotify/inotify_fsnotify.c | 6 +-
fs/notify/inotify/inotify_user.c | 16 ++--
fs/notify/mark.c | 140 ++++++++++++++----------------
include/linux/fs.h | 6 +-
include/linux/fsnotify_backend.h | 120 +++++++++++++++++++++-----
include/linux/fsnotify_obj.h | 14 +++
kernel/audit_fsnotify.c | 5 +-
kernel/audit_tree.c | 20 ++---
kernel/audit_watch.c | 7 +-
kernel/auditsc.c | 4 +-
20 files changed, 392 insertions(+), 311 deletions(-)
create mode 100644 include/linux/fsnotify_obj.h
--
2.7.4
next reply other threads:[~2018-04-20 23:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 23:10 Amir Goldstein [this message]
2018-04-20 23:10 ` [PATCH v3 01/13] fsnotify: use type id to identify connector object type Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 02/13] fsnotify: remove redundant arguments to handle_event() Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 03/13] fsnotify: introduce marks iteration helpers Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 04/13] fsnotify: generalize iteration of marks by object type Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 05/13] fsnotify: generalize send_to_group() Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 06/13] fanotify: generalize fanotify_should_send_event() Amir Goldstein
2018-05-18 10:47 ` Jan Kara
2018-04-20 23:10 ` [PATCH v3 07/13] fsnotify: add fsnotify_add_inode_mark() wrappers Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 08/13] fsnotify: introduce prototype struct fsnotify_obj Amir Goldstein
2018-05-18 12:02 ` Jan Kara
2018-04-20 23:10 ` [PATCH v3 09/13] fsnotify: pass fsnotify_obj instead of **connp argument Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 10/13] fsnotify: pass object and object type to fsnotify_add_mark() Amir Goldstein
2018-04-20 23:10 ` [PATCH v3 11/13] fsnotify: add fsnotify_connector_inode() wrapper Amir Goldstein
2018-05-18 12:48 ` Jan Kara
2018-04-20 23:11 ` [PATCH v3 12/13] fsnotify: let connector point to abstract fsnotify_obj Amir Goldstein
2018-04-20 23:11 ` [PATCH v3 13/13] fanotify: factor out helpers to add/remove mark Amir Goldstein
2018-05-18 13:09 ` [PATCH v3 00/13] Preparing for fanotify super block marks Jan Kara
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=1524265861-6316-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.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).