linux-kernel - Re: problems with splice from /proc (was Linux 5.10-rc1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201028183359.GA2957431@kroah.com>
Date:   Wed, 28 Oct 2020 19:33:59 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Al Viro <viro@...iv.linux.org.uk>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: problems with splice from /proc (was Linux 5.10-rc1)

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@...uxfoundation.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