linux-kernel - Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200707271458.44391.bjorn.helgaas@hp.com>
Date:	Fri, 27 Jul 2007 14:58:44 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	"Shaohua Li" <shaohua.li@...el.com>,
	"Sébastien Dugué" 
	<sebastien.dugue@...l.net>,
	linux-kernel <linux-kernel@...r.kernel.org>, ambx1@....rr.com,
	akpm@...ux-foundation.org, lenb@...nel.org, rmk@....linux.org.uk,
	mjg59@...f.ucam.org, castet.matthieu@...e.fr
Subject: Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my serial console

On Friday 27 July 2007 02:35:30 pm Yinghai Lu wrote:
> On 7/27/07, Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> > Can you give a more detailed example?  Maybe that would help me understand
> > the problem you're seeing.
> >
> > And why is udev not sufficient to give the NICs persistent names?
> 
> yes. NIC on node1 become the eth0 instead of eth2.

We aren't doing threaded probes or anything yet, so on a given
machine, device names should be deterministic.

Of course, if you reconfigure the machine, the driver may find
devices in a different order and name them something different.
I don't see a way to avoid that.

And couldn't we use udev to associate a fixed name with a MAC
address?  Then the user could use the same persistent name,
regardless of the order in which the driver found the devices.

Bjorn
-
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/