From: Richard Weinberger <richard@nod.at>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
matt.fleming@intel.com, matthew.garrett@nebula.com,
jlee@suse.com
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia
Date: Fri, 08 Nov 2013 09:05:48 +0100 [thread overview]
Message-ID: <527C9B5C.6040509@nod.at> (raw)
In-Reply-To: <527C93B5.7010407@jp.fujitsu.com>
Am 08.11.2013 08:33, schrieb Yasuaki Ishimatsu:
> By following works, my system very often fails set_variable() to set new
> variable to efi variable storage and shows "efivars: set_variable() failed:
> status=-28" message.
>
> - commit 31ff2f20d9003e74991d135f56e503fe776c127c
> efi: Distinguish between "remaining space" and actually used space
> - commit 8c58bf3eec3b8fc8162fe557e9361891c20758f2
> x86,efi: Implement efi_no_storage_paranoia parameter
> - commit f8b8404337de4e2466e2e1139ea68b1f8295974f
> Modify UEFI anti-bricking code
>
> When booting my system, remaining space of efi variable storage is about
> 5KB. So there is no room that sets a new variable to the storage.
>
> According to above works, efi_no_storage_paranoia parameter was prepared
> for sane UEFI which can do gc and fulfills spec. But why need a system
> with a sane UEFI set the parameter? It is wrong. A system with a broken
> UEFI should set the parameter.
And how does one know that his UEFI is broken?
"Oh my board is briked because I wrote too much into a variable, maybe setting
efi_storage_paranoia would have saved me. Let's try with the next board..." ;)
Thanks,
//richard
next prev parent reply other threads:[~2013-11-08 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 7:33 [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia Yasuaki Ishimatsu
2013-11-08 8:05 ` Richard Weinberger [this message]
2013-11-08 8:46 ` Madper Xie
2013-11-08 9:34 ` Yasuaki Ishimatsu
2013-11-08 9:37 ` Richard Weinberger
2013-11-08 10:25 ` Yasuaki Ishimatsu
2013-11-08 10:29 ` Richard Weinberger
2013-11-08 10:32 ` Yasuaki Ishimatsu
2013-11-08 14:34 ` Matt Fleming
2013-11-11 8:52 ` Yasuaki Ishimatsu
2013-11-11 9:47 ` Madper Xie
2013-11-11 10:54 ` Matt Fleming
2013-11-19 3:03 ` Yasuaki Ishimatsu
2013-11-19 3:16 ` Madper Xie
2013-11-20 6:26 ` Yasuaki Ishimatsu
2013-11-20 8:08 ` joeyli
2013-11-21 9:13 ` Yasuaki Ishimatsu
2013-11-21 9:53 ` joeyli
2013-11-21 10:27 ` 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=527C9B5C.6040509@nod.at \
--to=richard@nod.at \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthew.garrett@nebula.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