From: Greg KH <firstname.lastname@example.org>
To: Christoph Hellwig <email@example.com>
Cc: Linus Torvalds <firstname.lastname@example.org>,
Al Viro <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: Re: problems with splice from /proc (was Linux 5.10-rc1)
Date: Wed, 28 Oct 2020 17:00:11 +0100 [thread overview]
Message-ID: <20201028160011.GA2784447@kroah.com> (raw)
On Tue, Oct 27, 2020 at 04:32:13PM +0000, Christoph Hellwig wrote:
> On Tue, Oct 27, 2020 at 10:17:25AM +0100, Greg KH wrote:
> > Ok, I couldn't get a clean merge of that old branch on top of your
> > 5.10-rc1 tree, so I can't give it a run-through. If you have an updated
> > series you want me to test, I'll be glad to do so.
> Can you give this branch a spin?
Sorry for the delay, took a while to get results due to other testing
Anyway, yes, this worked!
So feel free to add:
Tested-by: Greg Kroah-Hartman <email@example.com>
If you send those out.
Now I ran into a fnctl test that is failing when reading trying to run
splice on /proc/version (crazy tests), let me go see if I can do the
same thing you did for cpuinfo for all proc "single data" files...
next prev parent reply other threads:[~2020-10-29 2:11 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
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 [this message]
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).