Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sun, 27 Dec 2020 17:56:12 +0100
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Jussi Kivilinna <jussi.kivilinna@iki.fi>
Cc:     linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
        torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net,
        jslaby@suse.cz
Subject: Re: LXC broken with 5.10-stable?, ok with 5.9-stable (Re: Linux
 5.10.3)
Message-ID: <X+i8rPxFIkUziZYN@kroah.com>
References: <16089960203931@kroah.com>
 <5ab86253-7703-e892-52b7-e6a8af579822@iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5ab86253-7703-e892-52b7-e6a8af579822@iki.fi>
Precedence: bulk

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