From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: [RFC][PATCH 0/4] Sort out fsnotify_nameremove() mess
Date: Wed, 15 May 2019 01:18:57 +0300 [thread overview]
Message-ID: <20190514221901.29125-1-amir73il@gmail.com> (raw)
Jan,
I started out working on your suggestion [1] of annotating
simple_unlink/rmdir_notify() callers when I realized we could
do better (IMO).
Please see this RFC. If you like the idea, I can split patches 3-4
to per filesystem patches and a final patch to make the switch from
fsnotify_nameremove() to fsnotify_remove().
I audited all the d_delete() call sites that will NOT generate
fsnotify events after these changes and noted to myself why that
makes sense. I will include those notes in next posting if this
works out for you.
Note that configfs got a special treatment, because its helpers
that call simple_unlink/rmdir() are called from both vfs_XXX code
path and non vfs_XXX code path.
Thanks,
Amir.
[1] https://lore.kernel.org/linux-fsdevel/20190513163309.GE13297@quack2.suse.cz/
Amir Goldstein (4):
fs: create simple_remove() helper
fsnotify: add empty fsnotify_remove() hook
fs: convert filesystems to use simple_remove() helper
fsnotify: move fsnotify_nameremove() hook out of d_delete()
arch/s390/hypfs/inode.c | 9 ++-----
drivers/infiniband/hw/qib/qib_fs.c | 3 +--
fs/afs/dir_silly.c | 5 ----
fs/btrfs/ioctl.c | 4 ++-
fs/configfs/dir.c | 3 +++
fs/dcache.c | 2 --
fs/debugfs/inode.c | 20 +++------------
fs/devpts/inode.c | 1 +
fs/libfs.c | 25 ++++++++++++++++++
fs/namei.c | 2 ++
fs/nfs/unlink.c | 6 -----
fs/notify/fsnotify.c | 41 ------------------------------
fs/tracefs/inode.c | 23 +++--------------
include/linux/fs.h | 1 +
include/linux/fsnotify.h | 18 +++++++++++++
include/linux/fsnotify_backend.h | 4 ---
net/sunrpc/rpc_pipe.c | 16 ++----------
security/apparmor/apparmorfs.c | 6 +----
18 files changed, 67 insertions(+), 122 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-14 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 22:18 Amir Goldstein [this message]
2019-05-14 22:18 ` [RFC][PATCH 1/4] fs: create simple_remove() helper Amir Goldstein
2019-05-15 7:51 ` Jan Kara
2019-05-14 22:18 ` [RFC][PATCH 2/4] fsnotify: add empty fsnotify_remove() hook Amir Goldstein
2019-05-15 7:57 ` Jan Kara
2019-05-14 22:19 ` [RFC][PATCH 3/4] fs: convert filesystems to use simple_remove() helper Amir Goldstein
2019-05-14 22:19 ` [RFC][PATCH 4/4] fsnotify: move fsnotify_nameremove() hook out of d_delete() Amir Goldstein
2019-05-15 8:24 ` Jan Kara
2019-05-15 10:56 ` Amir Goldstein
2019-05-15 11:45 ` Jan Kara
2019-05-15 8:36 ` [RFC][PATCH 0/4] Sort out fsnotify_nameremove() mess 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=20190514221901.29125-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).