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] [day] [month] [year] [list]
Message-ID: <20060915214354.GB24399@lists.us.dell.com>
Date:	Fri, 15 Sep 2006 16:43:54 -0500
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Greg KH <gregkh@...e.de>, akpm@...l.org
Cc:	Pierre Peiffer <pierre.peiffer@...l.net>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [Bug ??] 2.6.18-rc6-mm2 - PCI ethernet board does not seem to work

On Fri, Sep 15, 2006 at 03:29:54AM -0700, Greg KH wrote:
> That being said, I think we need to reverse the order of this patch,
> keeping the current scheme as default, and allowing it to be overridden
> on the command line for those few machines where it matters to be
> compatible with the old, 2.4 ordering scheme.
> 
> Matt, care to rework the patch in this manner?

Greg, Andrew,

I'd really like to rework this patch in a different direction.  As
such, please drop the patch:

gregkh-pci-pci-sort-device-lists-breadth-first.patch

from your trees, and I'll provide a new one next week.

Breadth-first vs depth-first is really only part of the problem.  More
fundamental is the expectation that embedded devices get discovered
before add-in devices in physical slots.  From there, breadth-first vs
depth-first is interesting again.  I'd like to sort the list to put
the embedded devices first, subsort those breadth-first, then list the
add-in devices in ascending slot number order, subsort breadth-first.
I'll default this sorting routine off, enabled/disabled via a command
line option, and enabled by default for some systems based on DMI
strings.

arch/i386/pci/irq.c already has the PCI IRQ Routing Table available,
from which we can get embedded vs slotN information.  It's not
currently being used in this manner, so I'm massaging that.

How does this sound?

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ