From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, Joel Stanley <joel@jms.id.au>,
David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
Kees Cook <keescook@chromium.org>,
"William A . Kennington III" <wak@google.com>,
Lei YU <mine260309@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jffs2: Hook up splice_write callback
Date: Wed, 31 Mar 2021 16:44:53 +0200 [thread overview]
Message-ID: <20210331144453.GA9931@lst.de> (raw)
In-Reply-To: <YGNuZMUkzH0tkce6@zeniv-ca.linux.org.uk>
On Tue, Mar 30, 2021 at 06:31:00PM +0000, Al Viro wrote:
> The same goes for quite a few other filesystems, actually - at least
> adfs, affs, bfs, hfs, hfsplus, hostfs, hpfs, minix, omfs, sysv, ufs
> and vboxsf are in the same boat, and I suspect that ecryptfs and ntfs
> might be too.
>
> Christoph, do you see any problems with doing the same thing for that
> bunch as well?
Linus asked to only fix things up where we get reports, but I think his
intent there was more random procfs and debugfs files rather than file
systems. So just doing the sweep should be fine.
next prev parent reply other threads:[~2021-03-31 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 13:45 [PATCH] jffs2: Hook up splice_write callback Joel Stanley
2021-03-30 16:17 ` Christoph Hellwig
2021-03-30 18:31 ` Al Viro
2021-03-30 18:38 ` Al Viro
2021-03-31 14:44 ` Christoph Hellwig [this message]
2021-03-31 4:55 ` Lei YU
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=20210331144453.GA9931@lst.de \
--to=hch@lst.de \
--cc=dwmw2@infradead.org \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mine260309@gmail.com \
--cc=richard@nod.at \
--cc=viro@zeniv.linux.org.uk \
--cc=wak@google.com \
/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