linux-kernel - Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <528AD50D.6060503@jp.fujitsu.com>
Date:	Tue, 19 Nov 2013 12:03:41 +0900
From:	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
To:	Matt Fleming <matt@...sole-pimps.org>
CC:	Richard Weinberger <richard@....at>, <linux-efi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <matt.fleming@...el.com>,
	<matthew.garrett@...ula.com>, <jlee@...e.com>
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter
 to efi_storage_paranoia

Hi Matt,

Sorry for late the reply.


(2013/11/11 19:54), Matt Fleming wrote:
> On Mon, 11 Nov, at 05:52:59PM, Yasuaki Ishimatsu wrote:
>> Hi Matt,
>>
>> I uses FUJITSU's x86 box.
>> This does not become bricked even if I use all efi variable storage.
>> Thus I want a way to not need to specify efi_no_storage_paranoia
>> parameter.
>
> The efi_no_storage_paranoia parameter was introduced because some
> machines do not initiate garbage collection of the NVRAM until you
> allocate all space - basically it's a switch to turn off the "save 5KB
> of stoarge at all times" workaround that is needed to avoid bricking
> some machines.
>
> The intention of the switch is not to allow you to fill your NVRAM just
> because you can. If that is something you want to do then I think it's
> fair to require you to explicitly turn on efi_no_storage_paranoia. But
> I'm assuming here that you are doing something like writing lots and
> lots of pstore entries and just want to write as many as your variable
> storage will allow? Or are you doing something more fundamental like
> creating BootXXXX entries?
>
> What are you doing to run into the 5KB reserve? How much NVRAM does your
> machine come with?

I just add boot entry to NVRAM by efibootmgr command. But when Linux boots up,
the remaining NVRAM is less than 5Kbyte. So I cannnot add new entry.

Thanks,
Yasuaki Ishimatsu

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/