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

Message-ID: <Pine.LNX.4.64.1210171021060.7402@axis700.grange>
Date:	Wed, 17 Oct 2012 10:27:36 +0200 (CEST)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	linux-kernel@...r.kernel.org
cc:	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: [Q] reprobe deferred-probing drivers

Hi

I've got a situation, for which I currently don't have a (good) solution.

Let's say device A depends on device B and as long as B hasn't probed, A 
requests deferred probing. Now B probes, which causes A to also succeed 
its probing. Next we want to remove B, say, by unloading its driver. A has 
to go back into "deferred-probing" state. How do we do it? This can be 
achieved by unloading B's driver and loading again. Essentially, we have 
to use the sysfs "unbind" and then the "bind" attributes. But how do we do 
this from the kernel? Shall we export driver_bind() and driver_unbind()?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.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/