From: Matt Domsch <Matt_Domsch@dell.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: matthew.e.tolentino@intel.com, linux-kernel@vger.kernel.org,
mactel-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH] - make sure that EFI variable data size is always 64 bit
Date: Sun, 19 Mar 2006 16:49:40 -0600 [thread overview]
Message-ID: <20060319224939.GA712@lists.us.dell.com> (raw)
In-Reply-To: <20060319213259.GA8602@srcf.ucam.org>
On Sun, Mar 19, 2006 at 09:33:01PM +0000, Matthew Garrett wrote:
> On Sun, Mar 19, 2006 at 03:29:01PM -0600, Matt Domsch wrote:
>
> > NAK. efibootmgr, the main userspace consumer of this struct, also
> > thinks this is an "unsigned long".
>
> Hm. My copy of efibootmgr has:
>
> typedef struct _efi_variable_t {
> efi_char16_t VariableName[1024/sizeof(efi_char16_t)];
> efi_guid_t VendorGuid;
> uint64_t DataSize;
> uint8_t Data[1024];
> efi_status_t Status;
> uint32_t Attributes;
> } __attribute__((packed)) efi_variable_t;
>
> which certainly makes it look like it's expecting a 64-bit value. But
> checking the spec does seem to suggest that datasize is a native value,
> so presumably it's an efibootmgr bug rather than a kernel one? In that
> case, this ought to be dropped.
Sorry, I did mean to post a link to the latest efibootmgr that has
this fixed:
Home page: http://linux.dell.com/efibootmgr/
For distros that care about 32-bit EFI, please upgrade to efibootmgr 0.5.3.
http://linux.dell.com/efibootmgr/efibootmgr-0.5.3.tar.gz
http://linux.dell.com/efibootmgr/efibootmgr-0.5.3.tar.gz.sign
http://linux.dell.com/efibootmgr/ChangeLog
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2006-03-19 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 18:43 [PATCH] - make sure that EFI variable data size is always 64 bit Matthew Garrett
2006-03-19 21:29 ` Matt Domsch
2006-03-19 21:33 ` Matthew Garrett
2006-03-19 22:49 ` Matt Domsch [this message]
2006-03-19 23:17 ` Matthew Garrett
2006-03-20 8:54 ` Pavel Machek
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=20060319224939.GA712@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mactel-linux-devel@lists.sourceforge.net \
--cc=matthew.e.tolentino@intel.com \
--cc=mjg59@srcf.ucam.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.