From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: linux-kernel@vger.kernel.org, Matthew Garrett <mjg@redhat.com>,
Matt Fleming <matt.fleming@intel.com>,
Matt Domsch <Matt_Domsch@Dell.com>
Subject: Re: [RFC,PATCH] efi: Add support for a UEFI variable filesystem
Date: Thu, 30 Aug 2012 10:22:39 -0700 [thread overview]
Message-ID: <503FA15F.7070506@zytor.com> (raw)
In-Reply-To: <1346319009.951368.767015086462.1.gpush@pecola>
On 08/30/2012 02:30 AM, Jeremy Kerr wrote:
> From: Matthew Garrett <mjg@redhat.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@canonical.com>.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@canonical.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
next parent reply other threads:[~2012-08-30 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1346319009.951368.767015086462.1.gpush@pecola>
2012-08-30 17:22 ` H. Peter Anvin [this message]
2012-08-31 0:42 ` [RFC,PATCH] efi: Add support for a UEFI variable filesystem Jeremy Kerr
2012-08-31 2:36 ` H. Peter Anvin
2012-09-03 1:39 ` Jeremy Kerr
2012-09-03 1:59 ` H. Peter Anvin
2012-09-03 3:15 ` Jeremy Kerr
2012-09-03 3:26 ` Matthew Garrett
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=503FA15F.7070506@zytor.com \
--to=hpa@zytor.com \
--cc=Matt_Domsch@Dell.com \
--cc=jeremy.kerr@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).