linux-kernel - Re: [PATCH 2/5] drivercore: Add driver probe deferral mechanism

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CACVXFVMnt-ChUDhawhoyMm-wJ8xSQAWs1c8ykzmyshfX49HEsw@mail.gmail.com>
Date:	Tue, 11 Oct 2011 20:29:18 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Andrei Warkentin <awarkentin@...are.com>
Cc:	Greg KH <greg@...ah.com>, Dilan Lee <dilee@...dia.com>,
	"G, Manjunath Kondaiah" <manjugk@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Josh Triplett <josh@...htriplett.org>,
	Grant Likely <grant.likely@...retlab.ca>, Manjunath@...per.es,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/5] drivercore: Add driver probe deferral mechanism

On Tue, Oct 11, 2011 at 1:37 AM, Andrei Warkentin <awarkentin@...are.com> wrote:
> Hi,
>
> ----- Original Message -----
>> From: "Greg KH" <greg@...ah.com>
>> To: "Josh Triplett" <josh@...htriplett.org>
>> Cc: "G, Manjunath Kondaiah" <manjugk@...com>, linux-arm-kernel@...ts.infradead.org, "Grant Likely"
>> <grant.likely@...retlab.ca>, linux-omap@...r.kernel.org, linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
>> "Dilan Lee" <dilee@...dia.com>, "Mark Brown" <broonie@...nsource.wolfsonmicro.com>, Manjunath@...per.es
>> Sent: Saturday, October 8, 2011 11:55:02 AM
>> Subject: Re: [PATCH 2/5] drivercore: Add driver probe deferral mechanism
>>
>
> I'm a bit of a fly on the wall here, but I'm curious how this impacts suspend/resume.
> device_initialize->device_pm_init are called from device_register, so certainly this
> patch doesn't also ensure that the PM ordering matches probe ordering, which is bound
> to break suspend, right? Was this ever tested with the OMAP target? Shouldn't the

Inside device_add(), device_pm_add is called before bus_probe_device,
so the patch can't change the device order in pm list, and just change
the driver probe order.

> PM change be also part of this patch set? I don't see why you would want to have this in
> without the PM changes.
>


thanks,
-- 
Ming Lei
--
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/