public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
To: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org,
	jlee-IBi9RG/b67k@public.gmane.org
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia
Date: Fri, 8 Nov 2013 19:32:51 +0900	[thread overview]
Message-ID: <527CBDD3.2020609@jp.fujitsu.com> (raw)
In-Reply-To: <527CBD01.1000908-/L3Ra7n9ekc@public.gmane.org>

(2013/11/08 19:29), Richard Weinberger wrote:
> Am 08.11.2013 11:25, schrieb Yasuaki Ishimatsu:
>> (2013/11/08 18:37), Richard Weinberger wrote:
>>> Am 08.11.2013 10:34, schrieb Yasuaki Ishimatsu:
>>>> (2013/11/08 17:05), Richard Weinberger wrote:
>>>>> 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?
>>>>
>>>> I have no idea. But at least, bricked board is broken UEFI.
>>>> Do you know the issue occurs on several boards or specific board?
>>>
>>> On *many* boards including laptops....
>>> Please read the history of the whole issue.
>>
>> Thank you for your comment.
>> I has read git log. But there is no information like this.
>> So I will read them of related threads again. Do you know good threads
>> to know the history of the issue?
> 

> Everything started with an issue that killed Samsung laptops:
> http://mjg59.dreamwidth.org/22855.html
> 
> Later it was found that if you write too much into UEFI variables many
> UEFI implementations will do bad things.

Thanks for the information.
I will read it.

Thanks,
Yasuaki Ishimatsu

> 
> Thanks,
> //richard
> 

  parent reply	other threads:[~2013-11-08 10:32 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
     [not found] ` <527C93B5.7010407-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-08  8:05   ` Richard Weinberger
     [not found]     ` <527C9B5C.6040509-/L3Ra7n9ekc@public.gmane.org>
2013-11-08  8:46       ` Madper Xie
2013-11-08  9:34       ` Yasuaki Ishimatsu
2013-11-08  9:37         ` Richard Weinberger
     [not found]           ` <527CB0F4.8080606-/L3Ra7n9ekc@public.gmane.org>
2013-11-08 10:25             ` Yasuaki Ishimatsu
2013-11-08 10:29               ` Richard Weinberger
     [not found]                 ` <527CBD01.1000908-/L3Ra7n9ekc@public.gmane.org>
2013-11-08 10:32                   ` Yasuaki Ishimatsu [this message]
     [not found]                     ` <527CBDD3.2020609-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-08 14:34                       ` Matt Fleming
     [not found]                         ` <20131108143421.GB22636-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-11-11  8:52                           ` Yasuaki Ishimatsu
     [not found]                             ` <52809AEB.9080100-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-11  9:47                               ` Madper Xie
2013-11-11 10:54                               ` Matt Fleming
     [not found]                                 ` <20131111105424.GD22636-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-11-19  3:03                                   ` Yasuaki Ishimatsu
     [not found]                                     ` <528AD50D.6060503-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-19  3:16                                       ` Madper Xie
     [not found]                                         ` <87siutqdwv.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-20  6:26                                           ` Yasuaki Ishimatsu
     [not found]                                             ` <528C562B.3070008-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-20  8:08                                               ` joeyli
2013-11-21  9:13                                                 ` Yasuaki Ishimatsu
     [not found]                                                   ` <528DCED7.5070806-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-21  9:53                                                     ` joeyli
     [not found]                                                       ` <1385027623.6516.4090.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
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=527CBDD3.2020609@jp.fujitsu.com \
    --to=isimatu.yasuaki-+cum20s59erqfuhtdcdx3a@public.gmane.org \
    --cc=jlee-IBi9RG/b67k@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org \
    --cc=richard-/L3Ra7n9ekc@public.gmane.org \
    /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