On Thu, 2008-12-25 at 17:36 +0000, Alan Jenkins wrote: > Odd. I have started and I've not seen anything like this. Maybe > you're > doing something wrong. I don't have time to look at or try your patch > today :-). > > libudev doesn't implement any locking itself. But AFAICS it's safe to > use *different* libudev objects such as udev_devices from different > threads. You generally don't need to modify the udev context object, so > it seemed safe to share the context between threads (and just make sure > to only call udev_ref/unref from a single thread). > I think I got it right, maybe I missed something that was in your original patch? The only vaguely unusual thing I was doing was running udevd in an existing booted system, and running udevadm trigger on that - so there would already have been udevdb entries for everything. Scott -- Scott James Remnant scott@xxxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
