linux-kernel - Re: [PATCH v2 1/3] drivers/bus: Add Legacy PM OPS usage check and warning to bus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 6 Jan 2014 12:17:55 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Shuah Khan <shuah.kh@...sung.com>
Cc:	rjw@...ysocki.net, shuahkhan@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] drivers/bus: Add Legacy PM OPS usage check and
 warning to bus_register()

On Mon, Jan 06, 2014 at 01:03:21PM -0700, Shuah Khan wrote:
> Add Legacy PM OPS usage checks to bus_register() function. If Legacy PM OPS
> usage is found, print warning message to indicate that the driver code needs
> updating to use Dev PM OPS interfaces. This will help serve as a way to track
> drivers that still use Legacy PM OPS and fix them.
> 
> The Legacy PM OPS check looks for suspend(struct device *, pm_message_t) or
> resume(struct device *) bus level interfaces.
> 
> Signed-off-by: Shuah Khan <shuah.kh@...sung.com>
> ---
>  drivers/base/bus.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> index 73f6c29..e8753a7 100644
> --- a/drivers/base/bus.c
> +++ b/drivers/base/bus.c
> @@ -916,6 +916,9 @@ int bus_register(struct bus_type *bus)
>  		goto bus_groups_fail;
>  
>  	pr_debug("bus: '%s': registered\n", bus->name);
> +	if (bus->suspend || bus->resume)
> +		pr_warn("bus '%s' needs updating - use pm pointer.\n",
> +			bus->name);

Why can't we just sweep the tree for all of these now, fix them up, and
then delete these fields and be done with it?

Same for the other ones, putting warnings in the kernel log files
doesn't work at all for getting people to fix up their code (see
examples of scsi log messages being there for _years_ about obsolete
driver interfaces being used.)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/