mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Michael Guntsche <mike@it-loops.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-hotplug <linux-hotplug@vger.kernel.org>
Subject: Re: [BUG] No ttyS0 - Strange udev 8250_pnp interaction
Date: Wed, 7 Oct 2009 22:06:13 +0200	[thread overview]
Message-ID: <ac3eb2510910071306r4ad6dc9btb7503bc3ab0ec815@mail.gmail.com> (raw)
In-Reply-To: <9b2b86520910071246r393f2afvacaa4d8f544508a8@mail.gmail.com>

On Wed, Oct 7, 2009 at 21:46, Alan Jenkins
<sourcejedi.lkml@googlemail.com> wrote:
> Udev would have avoided the race prior to
>
> 82c785e "udevd: remove check for dev_t, DEVPATH_OLD takes care of that"
>
> (the "check" removed here used to serialize events based on the device
> major:minor number).
>
> So - udev probably needs to add the check back.

What are the two devices with the same major/minor but a different DEVPATH?

> It might also be the case that future kernels could set DEVPATH_OLD as
> suggested.  I don't know the gory details of 8250_pnp though.

The DEVPATH_OLD is only added when one and the same device was renamed
or moved, which isn't the case here, I guess?

Kay

  reply	other threads:[~2009-10-07 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 17:54 Michael Guntsche
2009-10-07 19:46 ` Alan Jenkins
2009-10-07 20:06   ` Kay Sievers [this message]
2009-10-07 20:12     ` Kay Sievers
2009-10-07 20:31       ` Michael Guntsche
2009-10-07 20:53         ` Kay Sievers
2009-10-07 21:10           ` Alan Cox
2009-10-07 21:15             ` Kay Sievers
2009-10-07 21:23           ` Kay Sievers
2009-10-07 21:52             ` Michael Guntsche
2009-10-07 22:11               ` Kay Sievers

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=ac3eb2510910071306r4ad6dc9btb7503bc3ab0ec815@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@it-loops.com \
    --cc=sourcejedi.lkml@googlemail.com \
    /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

all inboxes | Powered by JetHome®