From: John Hubbard <jhubbard@nvidia.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Neil MacLeod <neil@nmacleod.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>
Subject: Re: Boot failure due to: x86/boot: Save fields explicitly, zero out everything else
Date: Wed, 21 Aug 2019 11:54:41 -0700 [thread overview]
Message-ID: <5b9b4c36-c28b-1644-61fe-dbdfe3c4a1d2@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1908212047140.1983@nanos.tec.linutronix.de>
On 8/21/19 11:51 AM, Thomas Gleixner wrote:
> On Wed, 21 Aug 2019, John Hubbard wrote:
>> On 8/21/19 10:05 AM, Neil MacLeod wrote:
>> static void sanitize_boot_params(struct boot_params *boot_params)
>> {
>> ...
>> const struct boot_params_to_save to_save[] = {
>> BOOT_PARAM_PRESERVE(screen_info),
>> BOOT_PARAM_PRESERVE(apm_bios_info),
>> BOOT_PARAM_PRESERVE(tboot_addr),
>> BOOT_PARAM_PRESERVE(ist_info),
>> BOOT_PARAM_PRESERVE(acpi_rsdp_addr),
>> BOOT_PARAM_PRESERVE(hd0_info),
>> BOOT_PARAM_PRESERVE(hd1_info),
>> BOOT_PARAM_PRESERVE(sys_desc_table),
>> BOOT_PARAM_PRESERVE(olpc_ofw_header),
>> BOOT_PARAM_PRESERVE(efi_info),
>> BOOT_PARAM_PRESERVE(alt_mem_k),
>> BOOT_PARAM_PRESERVE(scratch),
>> BOOT_PARAM_PRESERVE(e820_entries),
>> BOOT_PARAM_PRESERVE(eddbuf_entries),
>> BOOT_PARAM_PRESERVE(edd_mbr_sig_buf_entries),
>> BOOT_PARAM_PRESERVE(edd_mbr_sig_buffer),
>> BOOT_PARAM_PRESERVE(e820_table),
>> BOOT_PARAM_PRESERVE(eddbuf),
>> };
>
> I think I spotted it:
>
> - boot_params->acpi_rsdp_addr = 0;
>
> + BOOT_PARAM_PRESERVE(acpi_rsdp_addr),
>
> And it does not preserve 'hdr'
>
> Grr. I surely was too tired when staring at this last time.
>
ohhh man, that's embarrassing. Especially hdr, which was the center of
the whole thing...sigh. Patch coming shortly.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-08-21 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFbqK8m=F_90531wTiwKT4J0R+EC-3ZmqHtKCwA_2th_nVYrpg@mail.gmail.com>
2019-08-21 18:18 ` John Hubbard
2019-08-21 18:32 ` Neil MacLeod
2019-08-21 18:49 ` John Hubbard
2019-08-21 18:51 ` Thomas Gleixner
2019-08-21 18:54 ` John Hubbard [this message]
2019-08-21 19:49 ` Neil MacLeod
2019-08-21 20:00 ` John Hubbard
2019-08-21 18:56 ` Neil MacLeod
2019-08-21 19:25 ` [PATCH] x86/boot: Fix boot failure regression John Hubbard
2019-08-21 19:46 ` Neil MacLeod
2019-08-21 21:24 ` Thomas Gleixner
2019-08-22 12:30 ` Greg KH
2019-08-23 1:10 ` [tip: x86/urgent] x86/boot: Fix boot regression caused by bootparam sanitizing tip-bot2 for John Hubbard
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=5b9b4c36-c28b-1644-61fe-dbdfe3c4a1d2@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neil@nmacleod.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®