On Tue, 2013-03-12 at 16:14 -0500, Seth Forshee wrote: > From 91df4dd0d1e20f44ea16b3653cffecd507fdb500 Mon Sep 17 00:00:00 2001 > From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx> > Date: Wed, 6 Mar 2013 14:25:36 -0600 > Subject: [PATCH] efivars: Add module parameter to allow disabling use as a > pstore backend > > We know that with some firmware implementations writing too much data to > UEFI variables can lead to bricking machines. Recent changes attempt to > address this issue, but for some it may still be prudent to avoid > writing large amounts of data until the solution has been proven on a > wide variety of hardware. > > Crash dumps or other data from pstore can potentially be a large data > source. Add a pstore_enable parameter to efivars to allow disabling its > use as a backend for pstore. Also add a config option, > CONFIG_EFI_VARS_PSTORE, which will specify the default value for this > parameter. Default this option to Y to maintain the existing behavior. > > Signed-off-by: Seth Forshee <seth.forshee@xxxxxxxxxxxxx> > --- > drivers/firmware/Kconfig | 9 ++++++ > drivers/firmware/efivars.c | 66 +++++++++++++++----------------------------- > 2 files changed, 32 insertions(+), 43 deletions(-) Thanks for sticking with this Seth. I think this is a nice solution. I've tossed this patch into my urgent queue and tagged it for stable and added some Cc's. I did make one minor adjustment below. Let me know if you disagree. Peter, are you happy with this version? > diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig > index 9b00072..35f7d16 100644 > --- a/drivers/firmware/Kconfig > +++ b/drivers/firmware/Kconfig > @@ -53,6 +53,15 @@ config EFI_VARS > Subsequent efibootmgr releases may be found at: > <http://linux.dell.com/efibootmgr> > > +config EFI_VARS_PSTORE > + bool "Use efivars as a pstore backend" > + depends on EFI_VARS > + default y > + help > + Say Y here to enable the use of efivars as a storage backend > + for pstore. This setting can be overridden using the > + efivars.pstore_enable parameter. > + The depends here should probably include PSTORE, which I think it did on previous iterations. I can't think of a situation where you'd want to disable CONFIG_PSTORE but enable CONFIG_EFI_VARS_PSTORE. Also, we don't need to use CONFIG_EFI_VARS_PSTORE solely for the purpose of setting the initial value of efivars_pstore_enabled - there's merit in also using it to leave out the pstore code in efivars.c during compilation. Granted, this change does mean that your decision at compile time may be final, and you can't enable the pstore code at runtime if you built your kernel/efivars module with CONFIG_EFI_VARS_PSTORE=n. Arguably, I think that's a feature that some people will want, e.g. "Don't allow enabling the efivars pstore backend at all... no, srsly!". [...] > @@ -1309,8 +1312,6 @@ static const struct inode_operations efivarfs_dir_inode_operations = { > .create = efivarfs_create, > }; > > -static struct pstore_info efi_pstore_info; > - > #ifdef CONFIG_PSTORE ... I've changed this to #ifdef CONFIG_EFI_VARS_PSTORE, since if CONFIG_EFI_VARS_PSTORE=n there's no point compiling the pstore code. -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
