linux-kernel - [PATCH 0/8] PCI: cleanup pci_scan

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 23 Jan 2014 21:59:20 +0100
From:	Andreas Noever <andreas.noever@...il.com>
To:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	bhelgaas@...gle.com
Cc:	Andreas Noever <andreas.noever@...il.com>
Subject: [PATCH 0/8] PCI: cleanup pci_scan_bridge

I have been reading the code around pci_scan_bridge and noticed a few oddities.
These patches try to cleanup some of the these things.

Most of the patches make also sense in isolation, but some make more sense with
the previous ones applied as well. None of the patches fix any observed bugs.
Patch 5 fixes a (probably harmless) dmesg.

The changes related to CardBus probing are completely untested.

Andreas

Andreas Noever (8):
  PCI: Increment max correctly in pci_scan_bridge.
  PCI: Clarify the "scan anyway" comment in pci_scan_bridge.
  PCI: Assign CardBus bus number only during the second pass.
  PCI: Use request_resource_conflict instead of insert_ for bus numbers.
  PCI: Make sure bus number resources stay within their parents bounds.
  PCI: Remove pci_fixup_parent_subordinate_busnr.
  PCI: Check for child busses which use more bus numbers than allocated.
  PCI: Don't scan random busses in pci_scan_bridge.

 drivers/pci/probe.c | 78 +++++++++++++++++++++--------------------------------
 1 file changed, 31 insertions(+), 47 deletions(-)

-- 
1.8.5.3

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