[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5e40036f-b0da-47f3-acba-5dea9fdb7ed6@email.android.com>
Date: Thu, 30 Aug 2012 19:36:48 -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
Wouldn't that be better handled by O_APPEND?
Jeremy Kerr <jeremy.kerr@...onical.com> wrote:
>Hi hpa,
>
>Thanks for the review!
>
>> 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
>
>This will get tricky when handling EFI_VARIABLE_APPEND_WRITE: this
>attribute will never appear in the attributes returned by
>GetVariable(),
>but may be passed to SetVariable(). If we put attributes in the
>filename, we'd need to handle writes to both names, and/or have
>duplicate dentries for each variable. We could do it, but the
>filesystem
>interface might be a little messy.
>
>[Supporting append writes is essential for key database updates, which
>may be signed]
>
>Cheers,
>
>
>Jeremy
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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