linux-kernel - Re: Ordering hotplug scripts vs. udev device node creation

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]

Message-ID:  <453A6890.5030803@ciphirelabs.com>
Date:	Sat, 21 Oct 2006 20:36:00 +0200
From:	Andreas Jellinghaus <aj@...hirelabs.com>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Ordering hotplug scripts vs. udev device node creation

not sure, I ran into the same problem with usb device files
(both in /proc and /dev/bus/usb). and my quick hack was to simply
add a "sleep 1".

but there might be a cleaner solution:
with udevmonitor you should see what udev does, and it should
give you the name of the device it creates, so the call to udevinfo
should not be needed. and when that event with the device name
comes in - at least I hope - udev has already created it.

(at least I think it would be right if it creates a file to fire
the event associated with doing that after the mknod.)

maybe give it a try. reporting back here (or on the hotplug mailing
list which might be more appropriate) would be very welcome, as you
are not the only one running into these kind of problems.

good luck!

Andreas

-
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/