All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dexuan-Linux Cui <dexuan.linux@gmail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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,
	Dexuan Cui <decui@microsoft.com>
Subject: Re: Oops (probably) unmounting /oldroot/firmware/efi/efivars.
Date: Thu, 26 Nov 2020 12:09:55 -0800	[thread overview]
Message-ID: <CAA42JLYqy3Kb8Hrz9jFASwcN6KuC6H9SM3Mk1pFjCkUvBKt-zQ@mail.gmail.com> (raw)
In-Reply-To: <31d944b52416dd3fb82902566bc3b23b@natalenko.name>

On Wed, Nov 25, 2020 at 2:11 AM Oleksandr Natalenko
<oleksandr@natalenko.name> wrote:
>
> 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)

FYI, I hit the same issue with v5.10.0-rc5. It looks like the issue
has not been fixed in today's Linus tree.

Thanks,
Dexuan

      reply	other threads:[~2020-11-26 20: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
2020-11-26 20:09         ` Dexuan-Linux Cui [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=CAA42JLYqy3Kb8Hrz9jFASwcN6KuC6H9SM3Mk1pFjCkUvBKt-zQ@mail.gmail.com \
    --to=dexuan.linux@gmail.com \
    --cc=David.Laight@aculab.com \
    --cc=ardb@kernel.org \
    --cc=decui@microsoft.com \
    --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 \
    --cc=oleksandr@natalenko.name \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.