Re: waiting for an unknown set of udev /dev entries to complete

[md@Linux.IT (Marco d'Itri)]

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On Nov 21, Kay Sievers <kay.sievers@vrfy.org> wrote:

> > I still see a problem with this design: there is a period (which may be
> > easy to hit if the udevd is spawning the maximum allowed number of
> > children), between when events are sent to udevd and when it starts
> > processing them, when the on-disk queue is empty.
> It's the received event queue, which is exported, not the processes
> currently running. What problem do you see related to the maximum number
> of childs?
Nevermind, this makes the race much shorter but it's still there.

> There is still a small theorethical window between the module load
> and the first event for a device created by that module, but it's unlikely
> to hit that and it should be easy to work around that, if necessary.
Yes, this is what I meant (in the context of boot-time events synthesis)
and I do not like taking this risk.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]