[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1384963376.20536.3.camel@x230>
Date: Wed, 20 Nov 2013 16:02:57 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: "isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>
CC: "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"matt.fleming@...el.com" <matt.fleming@...el.com>,
"jlee@...e.com" <jlee@...e.com>,
"matt@...sole-pimps.org" <matt@...sole-pimps.org>,
"richard@....at" <richard@....at>,
"cxie@...hat.com" <cxie@...hat.com>
Subject: Re: [PATCH] x86, efi: add no_bricked_efi whitelist
On Wed, 2013-11-20 at 17:34 +0900, Yasuaki Ishimatsu wrote:
> 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. On my
> system, trigger of gc is when EFI_OUT_OF_RESOURCES occurs on pre OS
> environment with UEFI. So if EFI_OUT_OF_RESOURCES occurs by the 5Kbyte
> threshold, nvram storage cannot be used until EFI_OUT_OF_RESOURCES occurs
> on pre OS environment with UEFI.
By "remaining space is about 5KB", do you mean that the rest of the
space is filled with variables or do you mean that there is more free
space but it hasn't been garbage collected?
--
Matthew Garrett <matthew.garrett@...ula.com>
Powered by blists - more mailing lists