All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: problems with splice from /proc (was Linux 5.10-rc1)
Date: Wed, 28 Oct 2020 19:33:59 +0100	[thread overview]
Message-ID: <20201028183359.GA2957431@kroah.com> (raw)
In-Reply-To: <20201028160011.GA2784447@kroah.com>

On Wed, Oct 28, 2020 at 05:00:11PM +0100, Greg KH wrote:
> 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?
> > 
> > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/set_fs-proc
> 
> Sorry for the delay, took a while to get results due to other testing
> errors...
> 
> Anyway, yes, this worked!
> 
> So feel free to add:
> 
> 	Tested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> 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...

That worked too, I'll send a patch for this for the top of your branch
to resolve this issue as a response to this email.

thanks,

greg k-h

  reply	other threads:[~2020-10-28 22: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
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 [this message]
2020-10-28 18:34                   ` Christoph Hellwig
2020-10-28 18:35                   ` [PATCH] proc "single files": switch to ->read_iter Greg Kroah-Hartman

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=20201028183359.GA2957431@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.