Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <5f31cde519b941308412b3849197ee7c@AcuMS.aculab.com>
 <CAMj1kXHhetomAx4Kd5McnvZQev9j1d-C1Og7h+J7V009WTiwxA@mail.gmail.com>
 <c4c57a4b65d57bb7b2e87870a92558a5@natalenko.name> <X74WuTEjLXzAziwJ@kroah.com>
 <31d944b52416dd3fb82902566bc3b23b@natalenko.name>
In-Reply-To: <31d944b52416dd3fb82902566bc3b23b@natalenko.name>
From:   Dexuan-Linux Cui <dexuan.linux@gmail.com>
Date:   Thu, 26 Nov 2020 12:09:55 -0800
Message-ID: <CAA42JLYqy3Kb8Hrz9jFASwcN6KuC6H9SM3Mk1pFjCkUvBKt-zQ@mail.gmail.com>
Subject: Re: Oops (probably) unmounting /oldroot/firmware/efi/efivars.
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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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