linux-kernel - Re: tq 2440

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]

Message-ID: <20100716085533.GB2419@suse.de>
Date:	Fri, 16 Jul 2010 01:55:33 -0700
From:	Greg KH <gregkh@...e.de>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Conke Hu <conke.hu@...il.com>, CoffBeta <coffbeta@...il.com>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	inux kernel <linux-kernel@...r.kernel.org>,
	ext-jani.1.nikula@...ia.com,
	Uwe Kleine-K?nig <u.kleine-koenig@...gutronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: tq 2440

On Thu, Jul 15, 2010 at 10:09:36PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 15, 2010 at 01:51:53PM -0700, Greg KH wrote:
> > On Thu, Jul 15, 2010 at 06:33:22PM +0100, Russell King - ARM Linux wrote:
> > > Another way to avoid the other complaints is to remove
> > > the unregistration in platform_register_devices().
> > 
> > No, because you could have created a platform device with a call to
> > platform_device_alloc() and then called platform_device_register() and
> > then later, platform_device_unregister(), right?
> 
> No.  Sorry, platform_register_devices should've been platform_add_devices().
> Please look at that function.

Hm, it just calls platform_device_register(), so it's pretty hard to
determine that it's a static device from that function.

> It's used to register an array of static platform devices from architecture
> code, as I've said in this thread once already.

I can't think of an easy way to prevent these types of devices from
being removed, other than the existing warnings we have.  I'll mull it
over some more and see if I can come up with something in the future.

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/