MIME-Version: 1.0
In-Reply-To: <ac3eb2510910071306r4ad6dc9btb7503bc3ab0ec815@mail.gmail.com>
References: <20091007175403.GA335@trillian.comsick.at> <9b2b86520910071246r393f2afvacaa4d8f544508a8@mail.gmail.com> 
	<ac3eb2510910071306r4ad6dc9btb7503bc3ab0ec815@mail.gmail.com>
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Wed, 7 Oct 2009 22:12:28 +0200
Message-ID: <ac3eb2510910071312qe6ad45ep6c579a8393cc6b8e@mail.gmail.com>
Subject: Re: [BUG] No ttyS0 - Strange udev 8250_pnp interaction
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>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1145
Lines: 30

On Wed, Oct 7, 2009 at 22:06, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 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?

To be more specific, Michael, can you please run "udevadm monitor" at
the same time you see this happen?

>> 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?

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/