From mboxrd@z Thu Jan 1 00:00:00 1970 From: jdelvare@suse.de (Jean Delvare) Date: Thu, 20 Apr 2017 09:31:37 +0200 Subject: [PATCH 09/38] Annotate hardware config module parameters in drivers/i2c/ In-Reply-To: <149141148368.29162.12692004178864468110.stgit@warthog.procyon.org.uk> References: <149141141298.29162.5612793122429261720.stgit@warthog.procyon.org.uk> <149141148368.29162.12692004178864468110.stgit@warthog.procyon.org.uk> Message-ID: <20170420093137.5d28916d@endymion> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Wed, 05 Apr 2017 17:58:03 +0100, David Howells wrote: > When the kernel is running in secure boot mode, we lock down the kernel to > prevent userspace from modifying the running kernel image. Whilst this > includes prohibiting access to things like /dev/mem, it must also prevent > access by means of configuring driver modules in such a way as to cause a > device to access or modify the kernel image. > > To this end, annotate module_param* statements that refer to hardware > configuration and indicate for future reference what type of parameter they > specify. The parameter parser in the core sees this information and can > skip such parameters with an error message if the kernel is locked down. > The module initialisation then runs as normal, but just sees whatever the > default values for those parameters is. > > Note that we do still need to do the module initialisation because some > drivers have viable defaults set in case parameters aren't specified and > some drivers support automatic configuration (e.g. PNP or PCI) in addition > to manually coded parameters. > > This patch annotates drivers in drivers/i2c/. > > Suggested-by: Alan Cox > Signed-off-by: David Howells > cc: Wolfram Sang > cc: Jean Delvare > cc: linux-i2c at vger.kernel.org > (...) Acked-by: Jean Delvare -- Jean Delvare SUSE L3 Support -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html