[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <503FA15F.7070506@zytor.com>
Date: Thu, 30 Aug 2012 10:22:39 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Jeremy Kerr <jeremy.kerr@...onical.com>
CC: linux-kernel@...r.kernel.org, Matthew Garrett <mjg@...hat.com>,
Matt Fleming <matt.fleming@...el.com>,
Matt Domsch <Matt_Domsch@...l.com>
Subject: Re: [RFC,PATCH] efi: Add support for a UEFI variable filesystem
On 08/30/2012 02:30 AM, Jeremy Kerr wrote:
> From: Matthew Garrett <mjg@...hat.com>
>
> The existing EFI variables code only supports variables of up to 1024
> bytes. This limitation existed in version 0.99 of the EFI specification,
> but was removed before any full releases. Since variables can now be
> larger than a single page, sysfs isn't the best interface for this. So,
> instead, let's add a filesystem. Variables can be read, written and
> created, with the first 4 bytes of each variable representing its UEFI
> attributes. The create() method doesn't actually commit to flash since
> zero-length variables can't exist per-spec.
>
> Updates from Jeremy Kerr <jeremy.kerr@...onical.com>.
>
> Signed-off-by: Matthew Garrett <mjg@...hat.com>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@...onical.com>
>
> ---
> RFC: With this patch, I can properly mange UEFI key databases from
> userspace. Comments welcome.
>
Nice!
However, I have a question... rather than putting the attributes as the
first data bytes, would it be better to make it either part of the
filename (assuming there is at least one character other than / which
can be reasonably relied upon to not be part of the name); for example:
LangCodes,BS,RT
... or ...
LangCodes,6
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists