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: <CAE9FiQXaQMGytuWYcjWc6-CqfpLcdpZ=_TNke-ED6SUr2w8-9Q@mail.gmail.com>
Date:	Mon, 6 Feb 2012 10:48:41 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Tony Luck <tony.luck@...el.com>,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH 02/15] PCI: Add iobusn_resource

On Mon, Feb 6, 2012 at 9:14 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:

> The current bus number allocation in pci_scan_bridge() is very simple
> -- we just add one to the highest-numbered bridge we've seen.  That
> works in many cases, but it means any holes in the range of used bus
> numbers are just wasted.
>
> Here's a case I tripped over where the current scheme fails.  The
> machine boots with bridge 00:03.0 to [bus 05-19].  Now we hot-add a
> hierarchy that is currently configured like this:
>
>      05:00.0 bridge to [bus 06-1e]
>      06:05.0 bridge to [bus 1c]
>      06:06.0 bridge to [bus 1d]
>      1c:00.0 NIC0
>      1d:00.0 NIC1
>
> [bus 1a-1e] is inaccessible because the 00:03.0 aperture only includes
> [bus 05-19].  There's plenty of space to reconfigure the hierarchy,
> e.g., to make 05:00.0 lead to [bus 06-19], 06:05.0 lead to [bus 18],
> and 06:06.0 lead to [bus 19].  But we aren't smart enough to do that.

Yes, this patchset will reject 05:00.0 bus setting from bios, and
assign it with 06-19.

Yinghai
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ