linux-kernel - Re: [Q] reprobe deferred-probing drivers

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] [day] [month] [year] [list]

Message-ID: <CACVXFVO-h15jrcGbHe6v=wgTr3X3gQnB1Am4x376Mac=vEj3_w@mail.gmail.com>
Date:	Thu, 18 Oct 2012 00:02:24 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [Q] reprobe deferred-probing drivers

On Wed, Oct 17, 2012 at 4:43 PM, Guennadi Liakhovetski
<g.liakhovetski@....de> wrote:
> On Wed, 17 Oct 2012, Guennadi Liakhovetski wrote:
>
>> Hi
>>
>> I've got a situation, for which I currently don't have a (good) solution.
>
> Ok, right, would it be acceptable to just do something like
>
>                 if (dev->parent)
>                         device_lock(dev->parent);
>                 device_release_driver(dev);
>                 device_attach(dev);

The above should be OK for your purpose, and looks some other
deferred-probe devices may need this handling too.

But I am wondering how you could get the pointer of device A for
releasing driver in device B's remove()?

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/