From: Greg KH <email@example.com>
To: Christoph Hellwig <firstname.lastname@example.org>
Cc: Linus Torvalds <email@example.com>,
Al Viro <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: problems with splice from /proc (was Linux 5.10-rc1)
Date: Tue, 27 Oct 2020 09:14:20 +0100 [thread overview]
Message-ID: <20201027081420.GA30177@kroah.com> (raw)
On Tue, Oct 27, 2020 at 08:07:45AM +0000, Christoph Hellwig wrote:
> On Tue, Oct 27, 2020 at 08:55:41AM +0100, Greg KH wrote:
> > This is just a test, part of the bionic test suite to verify that bionic
> > is working properly, and is run on new kernels as a verification that
> > nothing functional broke in the kernel update.
> > I don't know about "real applications" yet.
> > Do you have to implement this on a per-proc-file-basis, or will it work
> > for the whole filesystem?
> > And are the patches public anywhere that I could test them out?
> This all branch has the last posted version:
> with tthe proc:, sysctl: and seq_file: patches related to it. It did
> switch over all seq_file instances, but non-seq_file instances and write
> operations will need manual per-instance work.
Luckily /proc/cpuinfo seems to use the seq_file interface, so this
series would work for that.
What's the odds of this series getting into 5.10-final? I'll go run it
through the Android build system right now to see if it fixes the issue
next prev parent reply other threads:[~2020-10-27 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 22:40 Linux 5.10-rc1 Linus Torvalds
2020-10-25 23:43 ` linux-next: stats Stephen Rothwell
2020-10-27 6:48 ` problems with splice from /proc (was Linux 5.10-rc1) Greg KH
2020-10-27 7:49 ` Christoph Hellwig
2020-10-27 7:55 ` Greg KH
2020-10-27 8:07 ` Christoph Hellwig
2020-10-27 8:14 ` Greg KH [this message]
2020-10-27 8:14 ` Christoph Hellwig
2020-10-27 9:17 ` Greg KH
2020-10-27 16:32 ` Christoph Hellwig
2020-10-27 17:43 ` Greg KH
2020-10-28 16:00 ` Greg KH
2020-10-28 18:33 ` Greg KH
2020-10-28 18:34 ` Christoph Hellwig
2020-10-28 18:35 ` [PATCH] proc "single files": switch to ->read_iter Greg Kroah-Hartman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).