| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <ac3eb2510910071312qe6ad45ep6c579a8393cc6b8e@mail.gmail.com> Date: Wed, 7 Oct 2009 22:12:28 +0200 From: Kay Sievers <kay.sievers@...y.org> To: Alan Jenkins <sourcejedi.lkml@...glemail.com> Cc: Michael Guntsche <mike@...loops.com>, linux-kernel <linux-kernel@...r.kernel.org>, linux-hotplug <linux-hotplug@...r.kernel.org> Subject: Re: [BUG] No ttyS0 - Strange udev 8250_pnp interaction On Wed, Oct 7, 2009 at 22:06, Kay Sievers <kay.sievers@...y.org> wrote: > On Wed, Oct 7, 2009 at 21:46, Alan Jenkins > <sourcejedi.lkml@...glemail.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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists