From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
David Laight <David.Laight@aculab.com>,
linux-efi <linux-efi@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
matthew.garrett@nebula.com, jk@ozlabs.org
Subject: Re: Oops (probably) unmounting /oldroot/firmware/efi/efivars.
Date: Wed, 25 Nov 2020 11:10:18 +0100 [thread overview]
Message-ID: <31d944b52416dd3fb82902566bc3b23b@natalenko.name> (raw)
In-Reply-To: <X74WuTEjLXzAziwJ@kroah.com>
Hello.
On 25.11.2020 09:32, Greg Kroah-Hartman wrote:
> On Tue, Nov 24, 2020 at 10:24:27PM +0100, Oleksandr Natalenko wrote:
>> Hi.
>>
>> On 24.11.2020 15:23, Ard Biesheuvel wrote:
>> > Surely caused by
>> >
>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/efivarfs?id=fe5186cf12e30facfe261e9be6c7904a170bd822
>>
>> This also soaked through the stable queue into v5.9.11, and now the
>> same BUG
>> is triggered in the latest stable kernel.
>>
>> /cc Greg
>
> cc: me for what?
>
> /me has no context as to what to do here...
This was a precursor to
https://lore.kernel.org/stable/X74VBej49SCPVisA@kroah.com/ and you
already jumped in there.
Thanks.
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2020-11-25 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:22 Oops (probably) unmounting /oldroot/firmware/efi/efivars David Laight
2020-11-24 14:23 ` Ard Biesheuvel
2020-11-24 14:42 ` David Laight
2020-11-24 14:57 ` David Laight
2020-11-24 15:01 ` Ard Biesheuvel
2020-11-24 15:30 ` David Laight
2020-11-24 21:24 ` Oleksandr Natalenko
2020-11-25 8:32 ` Greg Kroah-Hartman
2020-11-25 10:10 ` Oleksandr Natalenko [this message]
2020-11-26 20:09 ` Dexuan-Linux Cui
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=31d944b52416dd3fb82902566bc3b23b@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=David.Laight@aculab.com \
--cc=ardb@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
/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