From: Jussi Kivilinna <jussi.kivilinna@iki.fi>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: LXC broken with 5.10-stable?, ok with 5.9-stable (Re: Linux 5.10.3)
Date: Sun, 27 Dec 2020 18:32:41 +0200 [thread overview]
Message-ID: <5ab86253-7703-e892-52b7-e6a8af579822@iki.fi> (raw)
In-Reply-To: <16089960203931@kroah.com>
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?
-Jussi
On 26.12.2020 17.20, Greg Kroah-Hartman wrote:
> I'm announcing the release of the 5.10.3 kernel.
>
> All users of the 5.10 kernel series must upgrade.
>
> The updated 5.10.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
> thanks,
>
> greg k-h
>
> ------------
next prev parent reply other threads:[~2020-12-27 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 15:20 Linux 5.10.3 Greg Kroah-Hartman
2020-12-26 15:20 ` Greg Kroah-Hartman
2020-12-27 16:32 ` Jussi Kivilinna [this message]
2020-12-27 16:56 ` LXC broken with 5.10-stable?, ok with 5.9-stable (Re: Linux 5.10.3) Greg Kroah-Hartman
2020-12-27 17:20 ` Linus Torvalds
2020-12-27 18:39 ` Jussi Kivilinna
2020-12-27 19:05 ` Linus Torvalds
2020-12-27 20:12 ` Linus Torvalds
2020-12-27 21:25 ` Al Viro
2020-12-27 23:14 ` Linus Torvalds
2020-12-27 21:07 ` Jussi Kivilinna
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=5ab86253-7703-e892-52b7-e6a8af579822@iki.fi \
--to=jussi.kivilinna@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).