From: Sergey Fionov <fionov@gmail.com>
To: Matthew Garrett <matthew.garrett@nebula.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi: be more paranoid about available space when creating variables
Date: Mon, 25 Mar 2013 03:59:56 +0400 [thread overview]
Message-ID: <514F937C.9020203@gmail.com> (raw)
In-Reply-To: <1362271217-31747-1-git-send-email-matthew.garrett@nebula.com>
Hello.
My ASUS P8Z68-V PRO motherboard's UEFI cleans up EFI variables space
only if it is full when system boots.
So with this patch and 32kb of 64kb space used I can't use efibootmgr
to create new boot entries until EFI variables space become full and
then is cleaned up by UEFI.
It can be done only with 10 reboots (every boot uses 3 kilobytes of
EFI variables space) or patched efivars module.
I think it is a regression.
wbr,
Sergey.
prev parent reply other threads:[~2013-03-25 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 0:40 [PATCH] efi: be more paranoid about available space when creating variables Matthew Garrett
2013-03-03 0:40 ` Matthew Garrett
[not found] ` <1362271217-31747-1-git-send-email-matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
2013-03-04 20:24 ` Matt Fleming
2013-03-04 20:24 ` Matt Fleming
2013-03-24 23:59 ` Sergey Fionov [this message]
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=514F937C.9020203@gmail.com \
--to=fionov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.