linux-kernel - Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first

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: <20060909121134.GC4277@ucw.cz>
Date:	Sat, 9 Sep 2006 12:11:34 +0000
From:	Pavel Machek <pavel@....cz>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Andrew Morton <akpm@...l.org>, Matt Domsch <Matt_Domsch@...l.com>,
	linux-pci@...ey.karlin.mff.cuni.cz, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first

Hi!

> I wanted to note what Martin Mares just raised in the 
> thread "State of the Linux PCI Subsystem for 2.6.18-rc6":
> 
> >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.
> 
> 
> I'm not siding with either Martin or Matt explicitly, 
> just noting that there are good arguments for both sides.

I agree with martin here. 'Lets break all the machines where people
are currently using 2.6.x, for benefit of people currently running
2.4.x' is *very* bad idea.
							Pavel
-- 
Thanks for all the (sleeping) penguins.
-
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/