linux-kernel - Re: [RFC,PATCH v2] 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]

Date:	Thu, 13 Sep 2012 21:41:26 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	joeyli <jlee@...e.com>
CC:	Peter Jones <pjones@...hat.com>, jeremy.kerr@...onical.com,
	Matthew Garrett <mjg@...hat.com>, linux-kernel@...r.kernel.org,
	Matt Domsch <Matt_Domsch@...l.com>, glin@...e.com
Subject: Re: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem

On 09/13/2012 08:45 PM, joeyli wrote:
> Hi Peter,
>
> 於 四，2012-09-13 於 09:52 -0400，Peter Jones 提到：
>> On Thu, 2012-09-13 at 16:10 +0800, joeyli wrote:
>>
>>> Do we have plan to create a new kobject add to /sys/firmware/efi for
>>> provide a fixed mount point to efivars fs?
>>> e.g. /sys/firmware/efi/efivars
>>>
>>> Or we just direct reuse current /sys/firmeware/efi/vars? But, that means
>>> we need think for the backward compatibility if choice reuse vars
>>> folder.
>>
>> I'm not sure that's a terribly large concern - if you haven't updated
>> your tools to use the new efivars, don't mount the new efivars.
>>
>
> Thanks for your comment!
>

I think it is wrong.  The new API should have a different path.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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