From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Integrate udevsettle with udevtrigger?
Date: Tue, 18 Apr 2006 02:30:34 +0000 [thread overview]
Message-ID: <44444F4A.1010108@ums.usu.ru> (raw)
In-Reply-To: <444421CE.3030206@kadzban.is-a-geek.net>
Bryan Kadzban wrote:
> (I basically cut-and-pasted udevsettle's code into the function; it's
> possible that something got screwed up there. The code compiles OK for
> me, though, and it hasn't leaked any more uevents than "udevtrigger &&
> udevsettle" over ~6-8 bootups. To check for leaks, I'm doing what
> Alexander did[1]: putting an ACTION="add" RUN+="bug" rule last,
> clearing out the /dev/bug file after the udevtrigger --wait call,
> sleeping 6 seconds, and looking for anything in /dev/bug. Both setups
> leak events in the presence of usb-storage devices, but I think that's a
> known issue. If I have only USB-HID devices plugged in, that works OK
> whether I use "udevtrigger --wait" or "udevtrigger && udevsettle".)
Does the leak go away if you use the "ub" driver instead of "usb-storage"?
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-04-18 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 23:16 Integrate udevsettle with udevtrigger? Bryan Kadzban
2006-04-18 2:30 ` Alexander E. Patrakov [this message]
2006-04-18 3:02 ` Alexander E. Patrakov
2006-04-18 3:14 ` Bryan Kadzban
2006-04-18 6:35 ` Marco d'Itri
2006-04-18 8:03 ` Kay Sievers
2006-04-18 16:00 ` Andrey Borzenkov
2006-04-18 23:39 ` Bryan Kadzban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44444F4A.1010108@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.