From: Tejun Heo <htejun@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev queue error
Date: Tue, 31 May 2011 15:31:39 +0000 [thread overview]
Message-ID: <20110531153139.GA9048@mtj.dyndns.org> (raw)
In-Reply-To: <BANLkTim9kJEroUeqpqNoE-tCRvxa5=nghw@mail.gmail.com>
Hello,
On Mon, May 30, 2011 at 10:06:49PM +0200, Kay Sievers wrote:
> Yeah, the fake cdrom on the stick seems pretty broken. It generates
> media-changed events on very open(), and udev runs open() for the new
> event, which ... creates the loop you are seeing.
Ugh... :-(
> We need to find a way to work around such issues in the kernel, I guess.
>
> Tejun, any idea?
Hmmm... a couple of questions.
* udev doesn't open device w/ O_EXCL, right?
* Does a MEDIA_CHANGE event trigger multiple opens? I _think_ if udev
opens only once, the event shouldn't be re-generated immediately.
It will happen on the next poll interval but it won't be a busy
loop.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-05-31 15:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:46 udev queue error Markus Rathgeb
2011-05-30 20:06 ` Kay Sievers
2011-05-31 15:31 ` Tejun Heo [this message]
2011-05-31 15:34 ` Markus Rathgeb
2011-05-31 15:40 ` Kay Sievers
2011-05-31 15:46 ` Kay Sievers
2011-06-01 1:39 ` Tejun Heo
2011-06-01 2:10 ` Kay Sievers
2011-06-01 4:42 ` Tejun Heo
2011-06-08 11:55 ` Kay Sievers
2011-06-09 11:54 ` Tejun Heo
2011-06-09 12:36 ` Kay Sievers
2011-06-12 12:28 ` Tejun Heo
2011-06-13 19:02 ` Kay Sievers
2011-06-14 20:24 ` Kay Sievers
2011-06-15 7:13 ` Tejun Heo
2011-06-15 9:34 ` Kay Sievers
2011-06-15 9:40 ` Tejun Heo
2011-06-18 21:41 ` Kay Sievers
2011-06-28 13:45 ` Tejun Heo
2011-06-28 15:53 ` Tejun Heo
2011-06-28 15:57 ` Tejun Heo
2011-06-28 22:20 ` Kay Sievers
2011-06-28 22:21 ` Kay Sievers
2011-06-29 20:54 ` Markus Rathgeb
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=20110531153139.GA9048@mtj.dyndns.org \
--to=htejun@gmail.com \
--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).