mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Kerr <jeremy.kerr@canonical.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: linux-kernel@vger.kernel.org, Matthew Garrett <mjg@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Matt Domsch <Matt_Domsch@Dell.com>,
	Peter Jones <pjones@redhat.com>
Subject: Re: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem
Date: Thu, 06 Sep 2012 22:37:30 +0800	[thread overview]
Message-ID: <5048B52A.6000602@canonical.com> (raw)
In-Reply-To: <1346941851.4244.87.camel@mfleming-mobl1.ger.corp.intel.com>

Hi Matt,

> I think this is the problematic chunk of code,
>
> static int efivars_unlink(struct inode *dir, struct dentry *dentry)
> {
>          struct efivar_entry *var = dentry->d_inode->i_private;
>          struct efivars *efivars = var->efivars;
>          efi_status_t status;
>
>          spin_lock(&efivars->lock);
>
>          status = efivars->ops->set_variable(var->var.VariableName,
>                                              &var->var.VendorGuid,
>                                              0, 0, NULL);
>
> For deleting authenticated variables Attributes, DataSize and Data need
> to be non-zero. I think DataSize == AuthInfo descriptor. Peter?

That's correct, but we can't use unlink to delete a secure variable, we 
need to do a write instead, in order to provide the authentication 
descriptor.

But yes, we may need to alter the efivars_file_write path so that such a 
write actually results in the dentry being removed...

Cheers,


Jeremy



  reply	other threads:[~2012-09-06 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  5:40 Jeremy Kerr
2012-09-06 14:18 ` Matt Fleming
2012-09-06 14:23   ` Jeremy Kerr
2012-09-06 14:30     ` Matt Fleming
2012-09-06 14:37       ` Jeremy Kerr [this message]
2012-09-06 14:46         ` Matt Fleming
     [not found] ` <CAGLnvc9BXAW8F8WWyDxuF1_J+0np3uqUBmknuJewOJHhe-mxvw@mail.gmail.com>
2012-09-13  8:08   ` Fwd: " joeyli
2012-09-13  8:10   ` joeyli
2012-09-13 13:52     ` Peter Jones
2012-09-14  3:45       ` joeyli
2012-09-14  4:41         ` H. Peter Anvin
2012-09-15  2:44           ` joeyli
2012-09-15  2:26   ` 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=5048B52A.6000602@canonical.com \
    --to=jeremy.kerr@canonical.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mjg@redhat.com \
    --cc=pjones@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

Powered by JetHome