From: Peter Jones <pjones@redhat.com>
To: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
"Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
glin@suse.com, "Lee, Chun-Yi" <jlee@suse.com>,
Matthew Garrett <mjg@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] efi: add efivars kobject to efi sysfs folder
Date: Thu, 4 Oct 2012 09:30:51 -0400 [thread overview]
Message-ID: <20121004133050.GA4133@eddie.install.bos.redhat.com> (raw)
In-Reply-To: <506D5220.8080307@canonical.com>
On Thu, Oct 04, 2012 at 05:08:48PM +0800, Jeremy Kerr wrote:
> Hi Matt,
>
> >Jeremy, did you want to pick this up as part of your series?
>
> I have this in my series, yes. I'm just working on the authenticated
> delete code, then will send out the next revision.
>
> Speaking of which - Peter: I've realised that doing a GetVariable()
> after the SetVariable is a much cleaner way of checking whether we
> need to drop the inode after an authenticated delete.
>
> Because the inode's size may not be simply updated by the write(),
> we should probably be doing a GetVariable() after an APPEND_WRITE,
> to read the new size. Rather than having a separate (and quite
> complex) code path to check for the delete case, we may as well use
> the same logic to determine if the variable has been deleted.
Yeah, this is fine.
> >Actually, shouldn't the new filesystem be called "efivarfs", or "efifs"
> >to make it more explicit that it is a filesystem?
>
> I'm not too fussed about the name, but +1 for efivarfs.
I like efivarfs for the name, as well.
> >We also need something in Documentation/filesystems/ describing the old
> >EFI variable method, why it's no longer any good, and why the new
> >filesystem is favoured. Does anybody have anything to add to the
> >following?
>
> Looks good to me. We can always elaborate later, if necessary.
Yep.
--
Peter
next prev parent reply other threads:[~2012-10-04 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 2:24 [PATCH] efi: add efivars kobject to efi sysfs folder Lee, Chun-Yi
2012-10-04 8:54 ` Matt Fleming
2012-10-04 9:08 ` Jeremy Kerr
2012-10-04 13:30 ` Peter Jones [this message]
2012-10-04 9:46 ` joeyli
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=20121004133050.GA4133@eddie.install.bos.redhat.com \
--to=pjones@redhat.com \
--cc=glin@suse.com \
--cc=hpa@zytor.com \
--cc=jeremy.kerr@canonical.com \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=linux-efi@vger.kernel.org \
--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).