linux-kernel - Re: LXC broken with 5.10-stable?, ok with 5.9-stable (Re: Linux 5.10.3)

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]

Date:   Sun, 27 Dec 2020 17:56:12 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Jussi Kivilinna <jussi.kivilinna@....fi>
Cc:     linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
        torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
        jslaby@...e.cz
Subject: Re: LXC broken with 5.10-stable?, ok with 5.9-stable (Re: Linux
 5.10.3)

On Sun, Dec 27, 2020 at 06:32:41PM +0200, Jussi Kivilinna wrote:
> Hello,
> 
> Now that 5.9 series is EOL, I tried to move to 5.10.3. I ran in to regression where LXC containers do not start with newer kernel. I found that issue had been reported (bisected + with reduced test case) in bugzilla at: https://bugzilla.kernel.org/show_bug.cgi?id=209971
> 
> Has this been fixed in 5.11-rc? Is there any patch that I could backport and test with 5.10?

Have you tried Linus's tree to see if this works yet?  If not, it should
be a simple fix.  See 7cfc630e63b4 ("proc "single files": switch to
->read_iter") as an example of what is needed here.

I think we will see a lot of these "/proc files need to be fixed up"
issues over time as this is something that we hit in the 5.10-rc
sequence and fixed a bunch of them already...

thanks,

greg k-h