From: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>
To: matt@console-pimps.org
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Schroeder <mls@suse.com>, Josh Boyer <jwboyer@redhat.com>,
Jeremy Kerr <jeremy.kerr@canonical.com>,
"Lee, Chun-Yi" <jlee@suse.com>
Subject: [PATCH] efivarfs: fix abnormal GUID in variable name by using strcpy to replace null with dash
Date: Fri, 1 Mar 2013 11:20:18 +0800 [thread overview]
Message-ID: <1362108018-13117-1-git-send-email-jlee@suse.com> (raw)
From: Michael Schroeder <mls@suse.com>
On HP z220 system (firmware version 1.54), some EFI variables are incorrectly
named :
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
That causes by the following statement in efivar_create_sysfs_entry function:
*(short_name + strlen(short_name)) = '-';
efi_guid_unparse(vendor_guid, short_name + strlen(short_name));
The trailing \0 is overwritten with '-', but the next char doesn't seem to be a \0
as well for HP. So, the second strlen return the point of next '\0', causes there
have garbage string attached before GUID.
Tested on On HP z220.
Cc: Matt Fleming <matt@console-pimps.org>
Cc: Josh Boyer <jwboyer@redhat.com>
Cc: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: Michael Schroeder <mls@suse.com>
Reported-by: Frederic Crozat <fcrozat@suse.com>
Tested-by: Frederic Crozat <fcrozat@suse.com>
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
---
drivers/firmware/efivars.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/firmware/efivars.c b/drivers/firmware/efivars.c
index 8bcb595..fbf18ff 100644
--- a/drivers/firmware/efivars.c
+++ b/drivers/firmware/efivars.c
@@ -1708,7 +1708,7 @@ efivar_create_sysfs_entry(struct efivars *efivars,
/* This is ugly, but necessary to separate one vendor's
private variables from another's. */
- *(short_name + strlen(short_name)) = '-';
+ strcpy(short_name + strlen(short_name), "-");
efi_guid_unparse(vendor_guid, short_name + strlen(short_name));
new_efivar->kobj.kset = efivars->kset;
--
1.6.0.2
next reply other threads:[~2013-03-01 3:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 3:20 Lee, Chun-Yi [this message]
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
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=1362108018-13117-1-git-send-email-jlee@suse.com \
--to=joeyli.kernel@gmail.com \
--cc=jeremy.kerr@canonical.com \
--cc=jlee@suse.com \
--cc=jwboyer@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mls@suse.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®