linux-kernel - Re: [PATCH 1/3] efi: Add support for a UEFI variable filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1349551935.15966.59.camel@mfleming-mobl1.ger.corp.intel.com>
Date:	Sat, 06 Oct 2012 20:32:15 +0100
From:	Matt Fleming <matt.fleming@...el.com>
To:	Jeremy Kerr <jeremy.kerr@...onical.com>
Cc:	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	glin@...e.com, Lee@...nadilla.canonical.com,
	Chun-Yi <jlee@...e.com>, Matthew Garrett <mjg@...hat.com>,
	Peter Jones <pjones@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 1/3] efi: Add support for a UEFI variable filesystem

On Fri, 2012-10-05 at 13:54 +0800, 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>

Thanks, I've applied this series.

--
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/