linux-kernel - Re: State of the Linux PCI Subsystem for 2.6.18-rc6

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]

Date:	Sat, 9 Sep 2006 07:58:27 -0500
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Martin Mares <mj@....cz>
Cc:	Greg KH <gregkh@...e.de>, torvalds@...l.org,
	Andrew Morton <akpm@...l.org>,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org
Subject: Re: State of the Linux PCI Subsystem for 2.6.18-rc6

On Sat, Sep 09, 2006 at 10:39:32AM +0200, Martin Mares wrote:
> Hi Greg!
> 
> > No other new PCI driver API changes are pending that I am aware of.  The
> > PCI sort order change will affect some people's userspace ordering of
> > network devices, restoring it to the proper 2.4 ordering.  It was never
> > intended that this be broken, and since no one has noticed this for the
> > past 3 years, it was not broken in a severe way.
> 
> Changing the device order in the middle of the 2.6 cycle doesn't sound
> like a sane idea to me. Many people have changed their systems' configuration
> to adapt to the 2.6 ordering and this patch would break their setups.
> I have seen many such examples in my vicinity.
> 
> I believe that not breaking existing 2.6 setups is much more important
> than keeping compatibility with 2.4 kernels, especially when the problem
> is discovered after more than 2 years after release of the first 2.6.

Respectfully, With the current 2.6 development model (i.e. the lack of
a 2.7), how are we to address this kind of thing?  I'd like to see it
fixed in all new distro releases that base on 2.6.18-2.6.19, and it'll be an
individual distro decision to apply to existing releases (somewhat
unlikely).  I'm open to suggestions.  Udev rules like what opensuse
use would keep the existing names constant, as would the Red Hat
ifcfg-eth* method, so at least those distro users are OK.  We really
need this at install time to get the naming right in the first place.


-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
-
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/