From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Jörg Otte" <jrg.otte@gmail.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: EFI boot crash regression (was: Re: 5.6-### doesn't boot)
Date: Sat, 1 Feb 2020 23:36:11 +0100 [thread overview]
Message-ID: <CAKv+Gu8xcww0n9Apnb+ASeyb4pNVuMjJeopO-hC6NDAGQzVg3w@mail.gmail.com> (raw)
In-Reply-To: <CAPcyv4gPrJe2DSPyPJjJQLakEVs3w6x-jDVbX7iydw3D9C4iRQ@mail.gmail.com>
On Sat, 1 Feb 2020 at 23:31, Dan Williams <dan.j.williams@intel.com> wrote:
>
> On Sat, Feb 1, 2020 at 1:49 PM Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> >
> > On Sat, 1 Feb 2020 at 22:44, Dan Williams <dan.j.williams@intel.com> wrote:
> > >
> > > On Fri, Jan 31, 2020 at 10:45 AM Ard Biesheuvel
> > > <ard.biesheuvel@linaro.org> wrote:
> > > >
> > > > earlycon=efifb may help to get better diagnostics, but you will need to use a camera to capture the output
> > >
> > > https://photos.app.goo.gl/uA3Wkaxc8x6A4gK47
> >
> > Yeah, so it definitely has to do with the n_removal > 0 path.
> >
> > Did you try the change I suggested to Joerg?
>
> Nice, it worked.
>
> Tested-by: Dan Williams <dan.j.williams@intel.com>
Thanks for confirming. I'll spin a proper patch.
prev parent reply other threads:[~2020-02-01 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 17:32 5.6-### doesn't boot Jörg Otte
2020-01-30 18:07 ` Linus Torvalds
2020-01-30 18:22 ` Andy Lutomirski
2020-01-31 6:43 ` Ingo Molnar
2020-01-31 10:35 ` Jörg Otte
2020-01-31 18:36 ` EFI boot crash regression (was: Re: 5.6-### doesn't boot) Ingo Molnar
2020-01-31 18:48 ` Dan Williams
2020-02-01 15:35 ` Jörg Otte
2020-02-01 16:02 ` Ard Biesheuvel
2020-02-02 9:22 ` Ingo Molnar
2020-02-02 9:32 ` Ard Biesheuvel
2020-02-02 11:07 ` Jörg Otte
2020-02-03 7:45 ` Ingo Molnar
2020-02-01 21:29 ` Dan Williams
2020-02-01 9:45 ` [TEST PATCH RFC] Revert the EFI leak fixes for now (was: Re: EFI boot crash regression (was: Re: 5.6-### doesn't boot)) Ingo Molnar
2020-02-01 16:23 ` Dan Williams
[not found] ` <CAKv+Gu-oPrM7oh-oTbpQsUmXcYvp9KxjXFb3DUGk__qu59rdBQ@mail.gmail.com>
2020-02-01 21:44 ` EFI boot crash regression (was: Re: 5.6-### doesn't boot) Dan Williams
2020-02-01 21:49 ` Ard Biesheuvel
2020-02-01 22:31 ` Dan Williams
2020-02-01 22:36 ` Ard Biesheuvel [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=CAKv+Gu8xcww0n9Apnb+ASeyb4pNVuMjJeopO-hC6NDAGQzVg3w@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=jrg.otte@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 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.