From: Sasha Levin <sashal@kernel.org>
To: Andrew Macks <andypoo@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression in 4.14.147, 4.19.76, 5.2.18 leading to kernel panic on btrfs root fs mount
Date: Mon, 14 Oct 2019 00:20:23 -0400 [thread overview]
Message-ID: <20191014042023.GA31224@sasha-vm> (raw)
In-Reply-To: <CAFeYvHUoZdM5kY6LCfUiy6pVVf4VU_SWHtKeyevYenC3FZ7mng@mail.gmail.com>
On Sun, Oct 13, 2019 at 07:04:12PM +0300, Andrew Macks wrote:
>Was not sure the correct way to escalate this quickly enough. I
>unfortunately discovered this issue while upgrading a server (remotely) to
>4.19.78 (longterm).
>
>*Bug 205181* <https://bugzilla.kernel.org/show_bug.cgi?id=205181> - kernel
>panic when accessing btrfs root device with f2fs in kernel
>https://bugzilla.kernel.org/show_bug.cgi?id=205181
Okay, I've backported 38fb6d0ea3429 ("f2fs: use EINVAL for superblock
with invalid magic") to 4.19 and 4.14. It'll be great if someone could
ack that backport.
Sorry for the breakage.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-10-14 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 16:04 Regression in 4.14.147, 4.19.76, 5.2.18 leading to kernel panic on btrfs root fs mount Andrew Macks
2019-10-14 4:20 ` Sasha Levin [this message]
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=20191014042023.GA31224@sasha-vm \
--to=sashal@kernel.org \
--cc=andypoo@gmail.com \
--cc=linux-kernel@vger.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