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: <878uws1msy.fsf@redhat.com>
Date:	Wed, 13 Nov 2013 20:57:49 +0800
From:	Madper Xie <cxie@...hat.com>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	Madper Xie <cxie@...hat.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-efi\@vger.kernel.org" <linux-efi@...r.kernel.org>,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram.


matt@...sole-pimps.org writes:

> On Mon, 11 Nov, at 08:38:31PM, Madper Xie wrote:
>> 
>> matt@...sole-pimps.org writes:
>> 
>> > On Mon, 11 Nov, at 02:15:22PM, Madper Xie wrote:
>> >> Howdy all,
>> >>   For now we ensure at least ~5kb free space. But my dell xps still
>> >>   become a brick after I add too many entries to my nvram. So maybe 5kb
>> >>   is not safe enough. and 5kb is just aginst Samsung's laptop.
>> >>   So should we enlarge EFI_MIN_RESERVE?
>> >
>
> OK, that's pretty conclusive. Thanks.
>
Ouch, Sorry. My mistake. Seems filling too much entries to nvram is not
the murderer...
For testing, I using following command to fill my nvram:
head -c20480 /dev/urandom | efibootmgr --quiet --create --append-binary-args - 

For occupy lots of nvram space, I run it many times. But when I try to
find the threshold, I find the real murderer is that command. I mean my
dell xps will bricked even if I just run the command once and have more
than 100kb free space...

So the murderer is the new added boot entry. I don't really know if it's
still a bug. And I apologize for my mistake. :-(
>  
> Have you been able to calculate the safe limit of NVRAM we need to
> reserve to avoid bricking your machine?
>
> I was interested in the DMI and other firmware strings from dmesg.


-- 
Best,
Madper Xie.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ