[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170408151916.GA7879@kroah.com>
Date: Sat, 8 Apr 2017 17:19:16 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: David Howells <dhowells@...hat.com>
Cc: linux-kernel@...r.kernel.org, gnomes@...rguk.ukuu.org.uk,
linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
linux-serial@...r.kernel.org, Jiri Slaby <jslaby@...e.com>
Subject: Re: [PATCH 31/38] Annotate hardware config module parameters in
drivers/tty/
On Wed, Apr 05, 2017 at 06:01:26PM +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/tty/.
>
> Suggested-by: Alan Cox <gnomes@...rguk.ukuu.org.uk>
> Signed-off-by: David Howells <dhowells@...hat.com>
> cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> cc: Jiri Slaby <jslaby@...e.com>
> cc: linux-serial@...r.kernel.org
Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Powered by blists - more mailing lists