From: "Ed Tsai (蔡宗軒)" <Ed.Tsai@mediatek.com>
To: "willy@infradead.org" <willy@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"amir73il@gmail.com" <amir73il@gmail.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"miklos@szeredi.hu" <miklos@szeredi.hu>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"Chun-Hung Wu (巫駿宏)" <Chun-hung.Wu@mediatek.com>,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH 1/1] backing-file: covert to using fops->splice_write
Date: Sun, 7 Jul 2024 23:52:09 +0000 [thread overview]
Message-ID: <e2fc762dafb191b70557b1bab72ae5f50cdda69a.camel@mediatek.com> (raw)
In-Reply-To: <Zor9wiPTXCsnTVdt@casper.infradead.org>
On Fri, 2024-07-05 at 15:27 +0300, Amir Goldstein wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Fri, Jul 5, 2024 at 11:17 AM <ed.tsai@mediatek.com> wrote:
> >
> > From: Ed Tsai <ed.tsai@mediatek.com>
> >
> > Filesystems may define their own splice write. Therefore, use file
> > fops instead of invoking iter_file_splice_write() directly.
>
> This looks sane, but can you share the scenario where you ran into
> this?
> or did you find this via code audit?
>
> I can think of these cases:
> 1. overlayfs with fuse (virtiofs) upper
> 2. fuse passthrough over fuse
> 3. fuse passthrough over overlayfs
> 4. fuse passthrough over gfs2 or some out of tree fs
>
> The first two will not cause any harm,
> In case #3, according to the comment above ovl_splice_write()
> the current code could even deadlock.
>
> So do you have a reproduction?
>
> Thanks,
> Amir.
I came across this while checking what's new in the next LTS kernel.
This appears to be taken from overlayfs, and currently, no one has
encountered any issus about this.
On Sun, 2024-07-07 at 21:42 +0100, Matthew Wilcox wrote:
> On Fri, Jul 05, 2024 at 04:16:39PM +0800, ed.tsai@mediatek.com wrote:
> > +++ b/fs/backing-file.c
> > @@ -280,13 +280,16 @@ ssize_t backing_file_splice_write(struct
> pipe_inode_info *pipe,
> > if (WARN_ON_ONCE(!(out->f_mode & FMODE_BACKING)))
> > return -EIO;
> >
> > +if (out->f_op->splice_write)
> > +return -EINVAL;
>
> Umm ... shouldn't this have been !out->f_op->splice_write?
>
OMG... This is the wrong version. I will send the correct on later.
> > ret = file_remove_privs(ctx->user_file);
> > if (ret)
> > return ret;
> >
> > old_cred = override_creds(ctx->cred);
> > file_start_write(out);
> > -ret = iter_file_splice_write(pipe, out, ppos, len, flags);
> > +ret = out->f_op->splice_write(pipe, out, ppos, len, flags);
> > file_end_write(out);
> > revert_creds(old_cred);
> >
> > --
> > 2.18.0
> >
> >
>
prev parent reply other threads:[~2024-07-07 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 8:16 [PATCH 1/1] backing-file: covert to using fops->splice_write ed.tsai
2024-07-05 8:20 ` Ed Tsai (蔡宗軒)
2024-07-05 12:27 ` Amir Goldstein
2024-07-07 20:42 ` Matthew Wilcox
2024-07-07 23:52 ` Ed Tsai (蔡宗軒) [this message]
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=e2fc762dafb191b70557b1bab72ae5f50cdda69a.camel@mediatek.com \
--to=ed.tsai@mediatek.com \
--cc=Chun-hung.Wu@mediatek.com \
--cc=amir73il@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).