From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Josef Bacik <josef@toxicpanda.com>,
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: Re: [PATCH v2 08/16] btrfs: move file_start_write() to after permission hook
Date: Thu, 23 Nov 2023 17:54:00 +0100 [thread overview]
Message-ID: <20231123165400.akwegucagsbs32wg@quack3> (raw)
In-Reply-To: <20231122122715.2561213-9-amir73il@gmail.com>
On Wed 22-11-23 14:27:07, Amir Goldstein wrote:
> In vfs code, file_start_write() is usually called after the permission
> hook in rw_verify_area(). btrfs_ioctl_encoded_write() in an exception
> to this rule.
>
> Move file_start_write() to after the rw_verify_area() check in encoded
> write to make the permission hook "start-write-safe".
>
> This is needed for fanotify "pre content" events.
>
> Reviewed-by: Josef Bacik <josef@toxicpanda.com>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/btrfs/ioctl.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index dfe257e1845b..0a7850c4be67 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -4523,29 +4523,29 @@ static int btrfs_ioctl_encoded_write(struct file *file, void __user *argp, bool
> if (ret < 0)
> goto out_acct;
>
> - file_start_write(file);
> -
> if (iov_iter_count(&iter) == 0) {
> ret = 0;
> - goto out_end_write;
> + goto out_iov;
> }
> pos = args.offset;
> ret = rw_verify_area(WRITE, file, &pos, args.len);
> if (ret < 0)
> - goto out_end_write;
> + goto out_iov;
>
> init_sync_kiocb(&kiocb, file);
> ret = kiocb_set_rw_flags(&kiocb, 0);
> if (ret)
> - goto out_end_write;
> + goto out_iov;
> kiocb.ki_pos = pos;
>
> + file_start_write(file);
> +
> ret = btrfs_do_write_iter(&kiocb, &iter, &args);
> if (ret > 0)
> fsnotify_modify(file);
>
> -out_end_write:
> file_end_write(file);
> +out_iov:
> kfree(iov);
> out_acct:
> if (ret > 0)
> --
> 2.34.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-11-24 4:18 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 12:26 [PATCH v2 00/16] Tidy up file permission hooks Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 01/16] ovl: add permission hooks outside of do_splice_direct() Amir Goldstein
2023-11-23 7:35 ` Christoph Hellwig
2023-11-23 16:28 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 02/16] splice: remove permission hook from do_splice_direct() Amir Goldstein
2023-11-23 7:36 ` Christoph Hellwig
2023-11-23 16:28 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 03/16] splice: move permission hook out of splice_direct_to_actor() Amir Goldstein
2023-11-23 7:36 ` Christoph Hellwig
2023-11-23 16:35 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 04/16] splice: move permission hook out of splice_file_to_pipe() Amir Goldstein
2023-11-23 7:38 ` Christoph Hellwig
2023-11-23 16:37 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 05/16] splice: remove permission hook from iter_file_splice_write() Amir Goldstein
2023-11-23 7:47 ` Christoph Hellwig
2023-11-23 11:20 ` Amir Goldstein
2023-11-23 15:14 ` Christoph Hellwig
2023-11-23 15:41 ` Amir Goldstein
2023-11-23 15:45 ` Christoph Hellwig
2023-11-23 16:22 ` Christian Brauner
2023-11-23 16:53 ` Amir Goldstein
2023-11-23 17:56 ` Christian Brauner
2023-11-22 12:27 ` [PATCH v2 06/16] remap_range: move permission hooks out of do_clone_file_range() Amir Goldstein
2023-11-23 7:47 ` Christoph Hellwig
2023-11-23 16:52 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 07/16] remap_range: move file_start_write() to after permission hook Amir Goldstein
2023-11-23 7:48 ` Christoph Hellwig
2023-11-23 16:53 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 08/16] btrfs: " Amir Goldstein
2023-11-23 7:48 ` Christoph Hellwig
2023-11-23 16:54 ` Jan Kara [this message]
2023-11-22 12:27 ` [PATCH v2 09/16] coda: change locking order in coda_file_write_iter() Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 10/16] fs: move file_start_write() into vfs_iter_write() Amir Goldstein
2023-11-23 7:50 ` Christoph Hellwig
2023-11-23 8:04 ` Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 11/16] fs: move permission hook out of do_iter_write() Amir Goldstein
2023-11-22 14:33 ` Christian Brauner
2023-11-22 15:25 ` Amir Goldstein
2023-11-23 17:08 ` Jan Kara
2023-11-24 8:45 ` Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 12/16] fs: move permission hook out of do_iter_read() Amir Goldstein
2023-11-23 17:13 ` Jan Kara
2023-11-24 8:48 ` Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 13/16] fs: move kiocb_start_write() into vfs_iocb_iter_write() Amir Goldstein
2023-11-23 17:30 ` Jan Kara
2023-11-22 12:27 ` [PATCH v2 14/16] fs: create __sb_write_started() helper Amir Goldstein
2023-11-23 17:31 ` Jan Kara
2023-11-24 9:14 ` Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 15/16] fs: create file_write_started() helper Amir Goldstein
2023-11-22 12:27 ` [PATCH v2 16/16] fs: create {sb,file}_write_not_started() helpers Amir Goldstein
2023-11-23 17:35 ` Jan Kara
2023-11-24 8:20 ` Amir Goldstein
2023-12-01 10:11 ` Jan Kara
2023-11-22 14:06 ` [PATCH v2 00/16] Tidy up file permission hooks Josef Bacik
2023-11-22 15:04 ` Christian Brauner
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=20231123165400.akwegucagsbs32wg@quack3 \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--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