(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? -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html