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: <20201027091725.GA42707@kroah.com>
Date:   Tue, 27 Oct 2020 10:17:25 +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 Tue, Oct 27, 2020 at 09:14:20AM +0100, Greg KH wrote:
> 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:
> > 
> > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/set_fs-rw.2
> > 
> > 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
> or not...

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.

thanks,

greg k-h