From: Matthew Garrett <matthew.garrett@nebula.com>
To: "isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"matt.fleming@intel.com" <matt.fleming@intel.com>,
"jlee@suse.com" <jlee@suse.com>,
"matt@console-pimps.org" <matt@console-pimps.org>,
"richard@nod.at" <richard@nod.at>,
"cxie@redhat.com" <cxie@redhat.com>
Subject: Re: [PATCH] x86, efi: add no_bricked_efi whitelist
Date: Fri, 22 Nov 2013 17:48:34 +0000 [thread overview]
Message-ID: <1385142514.2884.2.camel@x230> (raw)
In-Reply-To: <528EF87D.4050300@jp.fujitsu.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 724 bytes --]
On Fri, 2013-11-22 at 15:23 +0900, Yasuaki Ishimatsu wrote:
> I don't know how to implement your idea. But if GC run by your idea, the free
> space may spread out. So 1) case is solved. But it does not solve 2) case.
> In my opinion, if system has sane firmware, all nvram strage should be used.
> I will send whiltelist version which used DMI infomation. Please review it.
We don't want to solve (2). The benefit in doing so is small compared to
the cost of maintaining a whitelist or risking breaking systems.
--
Matthew Garrett <matthew.garrett@nebula.com>
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
prev parent reply other threads:[~2013-11-22 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 8:34 [PATCH] x86, efi: add no_bricked_efi whitelist Yasuaki Ishimatsu
2013-11-20 8:54 ` Richard Weinberger
2013-11-21 9:25 ` Yasuaki Ishimatsu
2013-11-20 16:02 ` Matthew Garrett
2013-11-21 9:35 ` Yasuaki Ishimatsu
2013-11-21 20:12 ` Matthew Garrett
2013-11-22 0:00 ` Yasuaki Ishimatsu
2013-11-22 0:03 ` Matthew Garrett
2013-11-22 6:23 ` Yasuaki Ishimatsu
2013-11-22 6:29 ` [PATCH] x86, efi: add efi_whitelist_table to use all efi variable storage Yasuaki Ishimatsu
2013-11-22 17:47 ` Matthew Garrett
2013-12-03 3:20 ` Yasuaki Ishimatsu
2013-12-03 3:45 ` Matthew Garrett
2013-12-03 4:49 ` Yasuaki Ishimatsu
2013-12-03 5:04 ` Matthew Garrett
2013-12-03 5:12 ` Yasuaki Ishimatsu
2013-11-22 17:48 ` Matthew Garrett [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=1385142514.2884.2.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=cxie@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=richard@nod.at \
/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