summaryrefslogtreecommitdiffstats
path: root/drivers/mfd
diff options
context:
space:
mode:
authorMatthew Garrett <matthew.garrett@nebula.com>2013-03-03 01:40:17 +0100
committerMatt Fleming <matt.fleming@intel.com>2013-03-06 15:43:29 +0100
commit68d929862e29a8b52a7f2f2f86a0600423b093cd (patch)
tree2ae86a0b511deea1fd79b375297eedde45921a03 /drivers/mfd
parentLinux 3.9-rc1 (diff)
downloadlinux-68d929862e29a8b52a7f2f2f86a0600423b093cd.tar.xz
linux-68d929862e29a8b52a7f2f2f86a0600423b093cd.zip
efi: be more paranoid about available space when creating variables
UEFI variables are typically stored in flash. For various reasons, avaiable space is typically not reclaimed immediately upon the deletion of a variable - instead, the system will garbage collect during initialisation after a reboot. Some systems appear to handle this garbage collection extremely poorly, failing if more than 50% of the system flash is in use. This can result in the machine refusing to boot. The safest thing to do for the moment is to forbid writes if they'd end up using more than half of the storage space. We can make this more finegrained later if we come up with a method for identifying the broken machines. Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com> Cc: Josh Boyer <jwboyer@redhat.com> Cc: <stable@vger.kernel.org> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Diffstat (limited to 'drivers/mfd')
0 files changed, 0 insertions, 0 deletions