From: Hans de Goede <hdegoede@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Dominik Brodowski <linux@dominikbrodowski.net>,
the arch/x86 maintainers <x86@kernel.org>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 5.5 regression fix 2/2] efi/libstub/helper: Initialize pointer variables to zero for mixed mode
Date: Thu, 12 Dec 2019 13:38:40 +0100 [thread overview]
Message-ID: <9c5e89d7-7971-a0b4-fa56-fe4832007ca6@redhat.com> (raw)
In-Reply-To: <CAKv+Gu9AjYVvLot9+enuwSWfyfzqgCWSuW3ioccm3FJ7KFA8eA@mail.gmail.com>
Hi,
On 12-12-2019 12:29, Ard Biesheuvel wrote:
> On Thu, 12 Dec 2019 at 11:32, Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> When running in EFI mixed mode (running a 64 bit kernel on 32 bit EFI
>> firmware), we _must_ initialize any pointers which are returned by
>> reference by an EFI call to NULL before making the EFI call.
>>
>> In mixed mode pointers are 64 bit, but when running on a 32 bit firmware,
>> EFI calls which return a pointer value by reference only fill the lower
>> 32 bits of the passed pointer, leaving the upper 32 bits uninitialized
>> unless we explicitly set them to 0 before the call.
>>
>> We have had this bug in the efi-stub-helper.c file reading code for
>> a while now, but this has likely not been noticed sofar because
>> this code only gets triggered when LILO style file=... arguments are
>> present on the kernel cmdline.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> drivers/firmware/efi/libstub/efi-stub-helper.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/firmware/efi/libstub/efi-stub-helper.c b/drivers/firmware/efi/libstub/efi-stub-helper.c
>> index e02579907f2e..6ca7d86743af 100644
>> --- a/drivers/firmware/efi/libstub/efi-stub-helper.c
>> +++ b/drivers/firmware/efi/libstub/efi-stub-helper.c
>> @@ -365,7 +365,7 @@ static efi_status_t efi_file_size(efi_system_table_t *sys_table_arg, void *__fh,
>> u64 *file_sz)
>> {
>> efi_file_handle_t *h, *fh = __fh;
>
> What about h? Doesn't it suffer from the same problem?
>
>> - efi_file_info_t *info;
>> + efi_file_info_t *info = NULL;
>> efi_status_t status;
>> efi_guid_t info_guid = EFI_FILE_INFO_ID;
>> unsigned long info_sz;
>
> And info_sz?
You are right in both cases. I only checked allocate_pool and locate_protocol callers as those
are the usual suspects.
Shall I send a v2 of just this patch, or of the entire series, or are you going to
fix this up?
Regards,
Hans
>
>
>> @@ -527,7 +527,7 @@ efi_status_t handle_cmdline_files(efi_system_table_t *sys_table_arg,
>> unsigned long *load_addr,
>> unsigned long *load_size)
>> {
>> - struct file_info *files;
>> + struct file_info *files = NULL;
>> unsigned long file_addr;
>> u64 file_size_total;
>> efi_file_handle_t *fh = NULL;
>> --
>> 2.23.0
>>
>
next prev parent reply other threads:[~2019-12-12 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 10:31 [PATCH 5.5 regression fix 0/2] efi/libstub: Fix mixed-mode crash at boot Hans de Goede
2019-12-12 10:31 ` [PATCH 5.5 regression fix 1/2] efi/libstub/random: Initialize pointer variables to zero for mixed mode Hans de Goede
2019-12-12 10:37 ` Ard Biesheuvel
2019-12-12 10:31 ` [PATCH 5.5 regression fix 2/2] efi/libstub/helper: " Hans de Goede
2019-12-12 11:29 ` Ard Biesheuvel
2019-12-12 12:38 ` Hans de Goede [this message]
2019-12-12 12:45 ` Hans de Goede
2019-12-12 14:02 ` Ard Biesheuvel
2019-12-13 8:46 ` Ard Biesheuvel
2019-12-12 12:29 ` [PATCH 5.5 regression fix 0/2] efi/libstub: Fix mixed-mode crash at boot Dominik Brodowski
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=9c5e89d7-7971-a0b4-fa56-fe4832007ca6@redhat.com \
--to=hdegoede@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=stable@vger.kernel.org \
--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