linux-kernel - Re: [PATCH] platform_driver_register: warn if probe is in .init.text

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: <20090921075445.GA15833@pengutronix.de>
Date:	Mon, 21 Sep 2009 09:54:45 +0200
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Greg KH <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] platform_driver_register:  warn if probe is in
	.init.text

Hello Greg,

On Sat, Jul 11, 2009 at 10:05:48AM -0700, Greg KH wrote:
> On Sat, Jul 11, 2009 at 12:00:14PM +0200, Uwe Kleine-König wrote:
> > Hi Greg,
> > 
> > > > Are you conviced and took the patch or did you give up to convince me?
> > > 
> > > Heh, no, sorry, it got burried in my queue.
I assume this is normal for you? :-)

> > > > I still think the patch is correct and I'd like to have it applied.
> > > 
> > > Ok, let's test it out in the linux-next tree for a while to make sure it
> > > works properly.  Care to send me an updated version?
> > I updated to latest Linus' master.  It applies to linux-next from
> > Fri Jul 10 14:44:30 2009 +1000 as is.
> 
> Thanks, I'll apply it later today to my trees.
>
> > Back some time I sent a series that fixes many of these bugs.  I will
> > update it later today and resend.
> 
> Thanks, that would be good to have, to keep the noise down for devices
> we already know about.
As of today I don't see my patches in linux-next.  Are you still
interested?  Can I ease taking the patches for you somehow?  E.g. by
sending a tar containing a quilt series?

Do you think it would be more sensible to convert the drivers to use
platform_driver_probe as this is what some commentors request.
The downside is that these can result in regressions (i.e. no driver
binding if the device is created after the driver is registered).
So this would be merge-window material.

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |
--
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/