From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [systemd] v248.2 and later won't boot 4.19 kernel series
Date: Tue, 15 Jun 2021 17:39:13 +0200 [thread overview]
Message-ID: <YMjJocK3UcCLVl8H@kroah.com> (raw)
In-Reply-To: <a53e11ac-b2af-4410-9a7b-59a6ba8efca5@manjaro.org>
On Tue, Jun 15, 2021 at 04:59:27PM +0200, Philip Müller wrote:
> Hello all,
>
> with commit "mount-util: shortcut things after generating top-level bind
> mount" c2c331056a7c331a5478124b3cd6a34c9f539839
> (5c5753b9ea5cc012586ae90d357d460dec4301a4 in master) systemd 248.2 and
> later won't boot 4.19 kernel series. I tested 4.19.194 so far.
>
> Lennart's guess is that this is the mount table brokeness on old
> kernels, that newer libmount worked around. i.e. /proc/self/mountinfo on
> old kernels showed partially old data and partially new data, and
> confused the heck out of everyone. "proc on 20" with mount options
> "(rw,25)" doesn't look right at all.
>
> If we look at 4.14 and 4.4 kernel series, those boot. 4.9 I've still to
> test, as that one didn't boot either for me.
>
> So an idea what is missing in 4.19 kernel series? Other kernels work.
Do newer kernels work?
Any chance you can run 'git bisect' to find the offending kernel patch?
4.19 is really old, is this a stable-update-issue, or a "something
changed since 4.19 was released" type of issue?
> Systemd issue is this one: https://github.com/systemd/systemd/issues/19926
I'm running systemd 248.3 just fine here on 5.13-rc6, so this seems
odd...
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-15 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 14:59 [systemd] v248.2 and later won't boot 4.19 kernel series Philip Müller
2021-06-15 15:39 ` Greg Kroah-Hartman [this message]
2021-06-15 16:05 ` Philip Müller
2021-06-15 16:14 ` Greg Kroah-Hartman
2021-06-15 18:22 ` Philip Müller
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=YMjJocK3UcCLVl8H@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=philm@manjaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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