linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev queue error
Date: Thu, 09 Jun 2011 11:54:22 +0000	[thread overview]
Message-ID: <20110609115422.GF11773@htj.dyndns.org> (raw)
In-Reply-To: <BANLkTim9kJEroUeqpqNoE-tCRvxa5=nghw@mail.gmail.com>

Hello,

On Wed, Jun 08, 2011 at 01:55:01PM +0200, Kay Sievers wrote:
> Maybe we can find a clean way to disable the event generation during
> the time udev runs the event handler? We do a similar thing with
> inotify watches too, so that udev does not generate events it has
> caused itself during the event run.

Maybe we can tag events which were generated during open(2) with the
pid of the opener so that udev can reliably filter them?  I think it
would be nice if we can somehow make it uni-directional (ie. no extra
information from userland to kernel during open).

Thanks.

-- 
tejun

  parent reply	other threads:[~2011-06-09 11:54 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
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 [this message]
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=20110609115422.GF11773@htj.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).