linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/6] Prepare for fanotify name events
Date: Tue, 14 Jan 2020 17:16:49 +0200	[thread overview]
Message-ID: <20200114151655.29473-1-amir73il@gmail.com> (raw)

Jan,

Fanotify name event patches are ready at [1].
I am still updating the tests and the demo.

In the mean while, I wanted to post these few prep patches including
two bug fixes, so perhaps you will be able to process them in time for
v5.6-rc1.

Patches 1-4 are just cleanup and minor re-factoring in prep for the
name event patches.

Patches 5-6 are fixes for minor bug that I found during the work.
I improved ltp tests fanotify09 and fanotify15 to cover these bugs [2].

I did not mark those patches for stable, because backporting is not
trivial and the bugs are really minor.  For the same reason, I did
not bother to provide bug fix patches that are not dependent on the
cleanup patches, although that might have been possible to do.

Thanks,
Amir.

[1] https://github.com/amir73il/linux/commits/fanotify_name
[2] https://github.com/amir73il/ltp/commits/fsnotify-fixes

Amir Goldstein (6):
  fsnotify: tidy up FS_ and FAN_ constants
  fsnotify: pass dentry instead of inode for events possible on child
  fsnotify: simplify arguments passing to fsnotify_parent()
  fsnotify: replace inode pointer with tag
  fanotify: merge duplicate events on parent and child
  fanotify: fix merging marks masks with FAN_ONDIR

 fs/notify/fanotify/fanotify.c        | 36 ++++++++++++++++++++--------
 fs/notify/fsnotify.c                 | 21 ++++++++--------
 fs/notify/inotify/inotify_fsnotify.c |  2 +-
 include/linux/fsnotify.h             | 26 ++++++++------------
 include/linux/fsnotify_backend.h     | 34 +++++++++++++-------------
 include/uapi/linux/fanotify.h        |  4 ++--
 kernel/audit_fsnotify.c              |  5 +++-
 kernel/audit_watch.c                 |  5 +++-
 8 files changed, 73 insertions(+), 60 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-01-14 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 15:16 Amir Goldstein [this message]
2020-01-14 15:16 ` [PATCH 1/6] fsnotify: tidy up FS_ and FAN_ constants Amir Goldstein
2020-01-14 15:16 ` [PATCH 2/6] fsnotify: pass dentry instead of inode for events possible on child Amir Goldstein
2020-01-14 15:16 ` [PATCH 3/6] fsnotify: simplify arguments passing to fsnotify_parent() Amir Goldstein
2020-01-14 15:16 ` [PATCH 4/6] fsnotify: replace inode pointer with tag Amir Goldstein
2020-01-14 15:16 ` [PATCH 5/6] fanotify: merge duplicate events on parent and child Amir Goldstein
2020-01-14 15:16 ` [PATCH 6/6] fanotify: fix merging marks masks with FAN_ONDIR Amir Goldstein

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=20200114151655.29473-1-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).