From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [REPOST] uevent leak
Date: Sun, 26 Mar 2006 19:46:15 +0000 [thread overview]
Message-ID: <20060326234615.1828c0b0.vsu@altlinux.ru> (raw)
In-Reply-To: <442616D1.4020707@ums.usu.ru>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Sun, 26 Mar 2006 10:21:37 +0600 Alexander E. Patrakov wrote:
> The theory (well, not theory, just an unconfirmed guess) behind this
> bugreport, so far, is that udevd responds to uevents very quickly, faster
> than the kernel can deliver them from the netlink socket buffer. This leads
> to some moments when the queue is actually empty, and the loop exits
> prematurely.
Yes, the check for empty udev queue seems to be unreliable.
One way to make this reliable could be to trigger some kind of "sync"
event after all other events from udevtrigger, catch that event in an
udev rule and do something to notify the script (e.g., remove some
file). There is a problem, however: udevd can process events out of
order if their DEVPATH values do not overlap (see running_with_devpath()
in udevd.c), so the device for that event has to be really special.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-03-26 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 4:21 [REPOST] uevent leak Alexander E. Patrakov
2006-03-26 19:46 ` Sergey Vlasov [this message]
2006-03-26 21:05 ` Jürg Billeter
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=20060326234615.1828c0b0.vsu@altlinux.ru \
--to=vsu@altlinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).