From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Christoph Hellwig <hch@lst.de>,
David Howells <dhowells@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Miklos Szeredi <miklos@szeredi.hu>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 0/5] Prepare for fsnotify pre-content permission events
Date: Sun, 10 Dec 2023 16:18:56 +0200 [thread overview]
Message-ID: <20231210141901.47092-1-amir73il@gmail.com> (raw)
Hi Christian,
This v2 of pre-content event prep patches addresses some comments and
replaces the v1 patches [1] that are currently applied to vfs.rw.
I started with a new cleanup patch for ssize_t return type that you
suggested.
Patch 2 has a fix for a build error reported by kernel tests robot
(moved MAX_RW_COUNT capping to splice_file_range()), so I did not
retain the RVBs for this patch.
Patches 3,4 are unchanged and retain their RVBs.
Patch 5 changes the fsnotify hook name, so RBVs not retained.
Thanks,
Amir.
Changes since v1 [1]:
- Move MAX_RW_COUNT capping to splice_file_range() to fix build error
- Cleanup splice helpers return type
- Change fsnotify hook name to fsnotify_file_area_perm()
- Add RVBs
[1] https://lore.kernel.org/r/20231207123825.4011620-1-amir73il@gmail.com/
Amir Goldstein (5):
splice: return type ssize_t from all helpers
fs: use splice_copy_file_range() inline helper
fsnotify: split fsnotify_perm() into two hooks
fsnotify: assert that file_start_write() is not held in permission
hooks
fsnotify: optionally pass access range in file permission hooks
fs/ceph/file.c | 4 +--
fs/fuse/file.c | 5 +--
fs/nfs/nfs4file.c | 5 +--
fs/open.c | 4 +++
fs/overlayfs/copy_up.c | 2 +-
fs/read_write.c | 46 ++++++---------------------
fs/readdir.c | 4 +++
fs/remap_range.c | 8 ++++-
fs/smb/client/cifsfs.c | 5 +--
fs/splice.c | 69 ++++++++++++++++++++--------------------
include/linux/fs.h | 3 --
include/linux/fsnotify.h | 50 ++++++++++++++++++++---------
include/linux/splice.h | 50 ++++++++++++++++-------------
io_uring/splice.c | 4 +--
security/security.c | 10 ++----
15 files changed, 138 insertions(+), 131 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-10 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 14:18 Amir Goldstein [this message]
2023-12-10 14:18 ` [PATCH v2 1/5] splice: return type ssize_t from all helpers Amir Goldstein
2023-12-11 6:57 ` Amir Goldstein
2023-12-11 14:39 ` Jan Kara
2023-12-11 15:17 ` Amir Goldstein
2023-12-10 14:18 ` [PATCH v2 2/5] fs: use splice_copy_file_range() inline helper Amir Goldstein
2023-12-11 14:45 ` Jan Kara
2023-12-10 14:18 ` [PATCH v2 3/5] fsnotify: split fsnotify_perm() into two hooks Amir Goldstein
2023-12-10 14:19 ` [PATCH v2 4/5] fsnotify: assert that file_start_write() is not held in permission hooks Amir Goldstein
2023-12-10 14:19 ` [PATCH v2 5/5] fsnotify: optionally pass access range in file " Amir Goldstein
2023-12-11 15:20 ` 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=20231210141901.47092-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).