linux-kernel - Re: Probing unconfigured PCI bridge resouces

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: <1327380633.19850.33.camel@pasglop>
Date:	Tue, 24 Jan 2012 15:50:33 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	linux-pci@...r.kernel.org
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: Probing unconfigured PCI bridge resouces

On Tue, 2012-01-24 at 15:25 +1100, Benjamin Herrenschmidt wrote:
 .../...

> Or am I missing some important fact here ?

Ok, I think I was missing pci_bridge_check_ranges(), gotta figure now
why this didn't kick in properly for me, probably some arch code
crackpot.

One thing I noticed is that we do clear IORESOURCE_UNSET in setup-res.c
when setting up a device resource but we don't clear it for bridges in
generic code ever, so it leaks all the way through from my early arch
code. Not a big deal but annoying.

Cheers,
Ben.

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