linux-kernel - Re: [PATCH 7/7] initdev:kernel:Await block device discovery

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]

Date:	Tue, 09 Jun 2009 00:55:01 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	David VomLehn <dvomlehn@...co.com>
CC:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	linux-usb@...r.kernel.org, greg@...ah.com,
	linux-scsi@...r.kernel.org, netdev@...r.kernel.org,
	arjan@...radead.org
Subject: Re: [PATCH 7/7] initdev:kernel:Await block device discovery

David VomLehn wrote:
> On Sat, Jun 06, 2009 at 06:04:38AM -0400, Stefan Richter wrote:
>> 1.)  It depends on the rootdelay so big that it is guaranteed that one 
>> or more initdev_found() have been called before prepare_namespace()'s 
>> ssleep(root_delay) is over.
...
> I think you misunderstood.  Buses are enumerated before this code is
> reached and thus initdev_found() has already been called for all attached
> block devices.
...
> I would appreciate it if you could take a closer look at the locations where
> initdev_found() and initdev_probe_done() are called and see if you still
> think there is a problem.

I obviously need to do that.

However, one issue remains:  If somebody wants to use your API for 
another bus, he needs to know at which point he can successfully use it, 
and after what point (or context) it cannot, even must not, be used 
anymore.  This isn't documented --- or is it?

(By 'buses are enumerated before...' you surely mean only the buses for 
which you implemented this API usage already.)
-- 
Stefan Richter
-=====-==--= -==- -=--=
http://arcgraph.de/sr/
--
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/