summaryrefslogtreecommitdiffstats
path: root/sound/drivers
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2017-04-04 16:54:29 +0100
committerDavid Howells <dhowells@redhat.com>2017-04-20 12:02:32 +0100
commitb90fe0c4e0ceb52c78c17f3cfa1ff8e79275028d (patch)
treead5b9015a749a3c8570101bbdce84bb3cb408aec /sound/drivers
parent5d1c93ce21832825acc48595a6fec8cfdb3e1453 (diff)
downloadlinux-b90fe0c4e0ceb52c78c17f3cfa1ff8e79275028d.tar.bz2
Annotate hardware config module parameters in fs/pstore/
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 fs/pstore/. Suggested-by: Alan Cox <gnomes@lxorguk.ukuu.org.uk> Signed-off-by: David Howells <dhowells@redhat.com> Acked-by: Kees Cook <keescook@chromium.org> cc: Anton Vorontsov <anton@enomsg.org> cc: Colin Cross <ccross@android.com> cc: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'sound/drivers')
0 files changed, 0 insertions, 0 deletions