From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753251AbdDJKdV (ORCPT ); Mon, 10 Apr 2017 06:33:21 -0400 Received: from mail-pg0-f50.google.com ([74.125.83.50]:35006 "EHLO mail-pg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752251AbdDJKdT (ORCPT ); Mon, 10 Apr 2017 06:33:19 -0400 Date: Mon, 10 Apr 2017 16:03:16 +0530 From: Viresh Kumar To: David Howells Cc: linux-kernel@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk, linux-pm@vger.kernel.org, "Rafael J. Wysocki" , linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, gregkh@linuxfoundation.org Subject: Re: [PATCH 07/38] Annotate hardware config module parameters in drivers/cpufreq/ Message-ID: <20170410103316.GL24555@vireshk-i7> References: <149141141298.29162.5612793122429261720.stgit@warthog.procyon.org.uk> <149141146722.29162.13947802705058712127.stgit@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <149141146722.29162.13947802705058712127.stgit@warthog.procyon.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05-04-17, 17:57, 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/cpufreq/. > > Suggested-by: Alan Cox > Signed-off-by: David Howells > Acked-by: "Rafael J. Wysocki" > cc: Viresh Kumar > cc: linux-pm@vger.kernel.org > --- > > drivers/cpufreq/speedstep-smi.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/cpufreq/speedstep-smi.c b/drivers/cpufreq/speedstep-smi.c > index 770a9ae1999a..37b30071c220 100644 > --- a/drivers/cpufreq/speedstep-smi.c > +++ b/drivers/cpufreq/speedstep-smi.c > @@ -378,7 +378,7 @@ static void __exit speedstep_exit(void) > cpufreq_unregister_driver(&speedstep_driver); > } > > -module_param(smi_port, int, 0444); > +module_param_hw(smi_port, int, ioport, 0444); > module_param(smi_cmd, int, 0444); > module_param(smi_sig, uint, 0444); > Acked-by: Viresh Kumar -- viresh