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

Message-ID: <727e50150610231226p42b95cc4j686b31332c1d1c6e@mail.gmail.com>
Date:	Mon, 23 Oct 2006 15:26:14 -0400
From:	"Aaron Cohen" <aaron@...onance.org>
To:	linux-hotplug-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Ordering hotplug scripts vs. udev device node creation

(I sent this email to the linux kernel mailing list a couple of days
ago so the first couple of paragraphs may seem familiary to someone
who reads both lists.  I just found the hotplug list though, and have
some new details added.)

I'm trying to modify the gpsd hotplug script to work better with my
udev setup.  My USB serial devices are added to /dev/tts/USBx by udev
and the default script assumes they are /dev/ttyUSBx.

In any event, my hotplug script uses udevinfo to figure out the device
file to use.  The problem seems to be though that my hotplug script is
getting run before udev has actually created the device node.  Is
there some ordering mechanism I'm missing that would help me out here?

I am now using udev rules exclusively rather than old-style hotplug
rules.  I've created a file in /etc/udev/rules.d called 51-gpsd.rules
which contains:

KERNEL=="ttyUSB[0-9]*", RUN+="/lib/udev/gpsd"

/lib/udev/gpsd is my script that runs udevinfo to figure out the /dev/
file to use and communicates this to gpsd through a control socket.

Adding a USB device seems to work correctly (more or less, my script
is invoked a few too many times but I think I can figure out how to
adjust my rule) using this.  I'm having trouble now with removal
though.  By the time my script runs the device file has been removed
by udev and I can't look it up through udevinfo any longer.  I need to
know what the name of the device file was so I can tell gpsd to stop
monitoring it.

Any ideas?

Thanks,
Aaron
-
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/