From: Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Matthew Garrett
<matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
Cc: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>,
Josh Boyer <jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Seth Forshee
<seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: efi: be more paranoid about available space when creating variables
Date: Sat, 23 Mar 2013 22:50:24 +0000 [thread overview]
Message-ID: <514E31B0.4030305@intel.com> (raw)
In-Reply-To: <1364070731.2553.47.camel-tCUS0Eywp2Pehftex57rkxo58HMYffqeLoYNBG0abjxeoWH0uzbU5w@public.gmane.org>
(Let's try this again without using HTML)
On 23/03/13 20:32, Matthew Garrett wrote:
> On Sat, 2013-03-23 at 20:24 +0000, Fleming, Matt wrote:
>
>> Looks like we're going to have to go down the road of blacklisting
>> known bad machines after all. I was reluctant to push for that
>> originally as the result of missing a machine from the blacklist might
>> result in said machine becoming bricked, but we've now got patches in
>> place to turn off the pstore efivars code, and I suspect that most
>> distros indeed do that.
>
> Handwaving idea - leave the size restriction in place for pstore. Remove
> it for normal setvariable calls. Downside of this is that pstore will be
> broken on machines that only clear space when the variable store is
> mostly full, but it should avoid cases where we automatically kill
> machines without also having to disable a useful feature.
Right, but it will still be possible to brick machines via the code path
that doesnt check the remaining storage space. Its less likely sure, but
its still entirely possible.
The most robust solution may be to combine the two approaches - remove the
size checks from everything but the pstore paths but enforce them across
the board for known problem machines?
next prev parent reply other threads:[~2013-03-23 22:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1364004995.3728.76.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1364010441.3728.82.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1364010441.3728.82.camel-nDn/Rdv9kqW9Jme8/bJn5UCKIB8iOfG2tUK59QYPAWc@public.gmane.org>
2013-03-23 20:24 ` efi: be more paranoid about available space when creating variables Fleming, Matt
2013-03-23 20:32 ` Matthew Garrett
[not found] ` <1364070731.2553.47.camel-tCUS0Eywp2Pehftex57rkxo58HMYffqeLoYNBG0abjxeoWH0uzbU5w@public.gmane.org>
2013-03-23 22:50 ` Matt Fleming [this message]
[not found] ` <514E31B0.4030305-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-03-26 3:56 ` Matthew Garrett
2013-03-26 4:31 ` Lingzhu Xiang
[not found] ` <5151248F.2010303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-03-26 4:34 ` Ben Hutchings
2013-03-26 4:35 ` Matthew Garrett
[not found] ` <20130326035600.GA6209-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-26 7:40 ` Lingzhu Xiang
2013-04-01 15:13 ` [PATCH 1/2] efi: Determine how much space is used by boot services-only variables Matthew Garrett
[not found] ` <1364829240-26475-1-git-send-email-matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
2013-04-01 15:14 ` [PATCH 2/2] efi: Distinguish between "remaining space" and actually used space Matthew Garrett
[not found] ` <1364829240-26475-2-git-send-email-matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
2013-04-01 15:50 ` Ben Hutchings
2013-04-03 13:11 ` Matt Fleming
[not found] ` <515C2A86.6070606-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-03 13:48 ` Matthew Garrett
2013-04-03 17:12 ` Matt Fleming
[not found] ` <515C62E6.1070004-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-03 17:20 ` Matthew Garrett
2013-04-01 15:42 ` [PATCH 1/2] efi: Determine how much space is used by boot services-only variables Ben Hutchings
2013-04-03 13:09 ` Matt Fleming
[not found] ` <515C29EE.8050008-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-03 13:42 ` Matthew Garrett
2013-03-26 10:37 ` efi: be more paranoid about available space when creating variables Matt Fleming
2013-03-26 15:43 ` Matthew Garrett
[not found] ` <20130326154359.GA20530-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-27 9:09 ` Matt Fleming
[not found] ` <5152B75B.5080305-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-01 6:31 ` Ben Hutchings
2013-03-26 23:33 ` Seiji Aguchi
[not found] ` <A5ED84D3BB3A384992CBB9C77DEDA4D41AF79528-ohthHghroY0jroPwUH3sq+6wyyQG6/Uh@public.gmane.org>
2013-03-27 9:10 ` Matt Fleming
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=514E31B0.4030305@intel.com \
--to=matt.fleming-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org \
--cc=jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org \
--cc=seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).