mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Frederic Crozat <fcrozat@suse.com>
Cc: joeyli <jlee@suse.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michael Schroeder <mls@suse.com>, Josh Boyer <jwboyer@redhat.com>,
	Peter Jones <pjones@redhat.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] efivarfs: fix abnormal GUID in variable name by using strcpy to replace null with dash
Date: Wed, 06 Mar 2013 13:38:06 +0000	[thread overview]
Message-ID: <1362577086.15011.57.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1362576633.7004.69.camel@par-r81vxc7.par.novell.com>

On Wed, 2013-03-06 at 14:30 +0100, Frederic Crozat wrote:
> Le mercredi 06 mars 2013 à 12:36 +0000, Matt Fleming a écrit :
> > On Wed, 2013-03-06 at 12:58 +0100, Frederic Crozat wrote:
> > > Le mercredi 06 mars 2013 à 11:19 +0000, Matt Fleming a écrit :
> > > 
> > > > Also, which machine did you see this behaviour on?
> > > 
> > > HP z220 desktop, System BIOS K51 v 1.54
> > > 
> > > this issue is only the "Secure Boot" related variables, which make me
> > > think HP incorrectly created them in their latest firmware (where they
> > > added Windows 8 support).
> > 
> > Are you saying that the behaviour regarding VariableNameSize changes
> > depending on which variable is returned?
> >
> > Mercy.....
>  
> Well, I only get the error message for some variables (8), not all of
> them.
> 
> It was quite visible on unpatched kernel, with ls
> -d /sys/firmware/efi/vars. 
> 
> ls -d /sys/firmware/efi/vars/*8be4d* | grep -v -- -8be returns
> /sys/firmware/efi/vars/dbxDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/KEKDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SecureBoot-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SetupMode-Information8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SignatureSupport-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/VendorKeys-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> 
> All other variable names were fine.

Interesting. Thanks.

-- 
Matt Fleming, Intel Open Source Technology Center


  reply	other threads:[~2013-03-06 13:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01  3:20 Lee, Chun-Yi
2013-03-01  9:31 ` Lingzhu Xiang
2013-03-01 14:49   ` joeyli
2013-03-01 15:17 ` Matt Fleming
2013-03-01 16:31   ` Matt Fleming
2013-03-01 23:41     ` joeyli
2013-03-06  7:34       ` joeyli
2013-03-06  7:39         ` joeyli
2013-03-06  9:20         ` Lingzhu Xiang
2013-03-06 11:21           ` Matt Fleming
2013-03-07  8:03           ` joeyli
2013-03-06 11:19         ` Matt Fleming
2013-03-06 11:58           ` Frederic Crozat
2013-03-06 12:36             ` Matt Fleming
2013-03-06 13:30               ` Frederic Crozat
2013-03-06 13:38                 ` Matt Fleming [this message]
2013-03-07 10:34           ` joeyli
2013-03-07 11:39             ` Matt Fleming
2013-03-07 13:57               ` Matt Fleming
2013-03-07 14:03                 ` joeyli
2013-03-11 13:17                 ` joeyli
2013-03-18 15:29                   ` Matt Fleming
2013-03-08  6:37               ` 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=1362577086.15011.57.camel@mfleming-mobl1.ger.corp.intel.com \
    --to=matt@console-pimps.org \
    --cc=fcrozat@suse.com \
    --cc=jlee@suse.com \
    --cc=jwboyer@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=mls@suse.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

all inboxes | Powered by JetHome®