diff options
author | Bjorn Helgaas <bhelgaas@google.com> | 2014-03-10 10:46:56 -0600 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2014-03-19 15:00:16 -0600 |
commit | e20fa6609a0076def469aeb799b1c25558e70042 (patch) | |
tree | 7655a6a74f2fc9209e723af10e1b72ac7f127c04 /kernel | |
parent | d75332325389a95c4ddbfa0f0cd7e5e08a54aa43 (diff) | |
download | linux-e20fa6609a0076def469aeb799b1c25558e70042.tar.gz linux-e20fa6609a0076def469aeb799b1c25558e70042.tar.bz2 linux-e20fa6609a0076def469aeb799b1c25558e70042.zip |
PCI: Don't check resource_size() in pci_bus_alloc_resource()
Paul reported that after f75b99d5a77d ("PCI: Enforce bus address limits in
resource allocation") on a 32-bit kernel (CONFIG_PHYS_ADDR_T_64BIT not
set), intel-gtt complained "can't ioremap flush page - no chipset
flushing". In addition, other PCI resource allocations, e.g., for bridge
windows, failed.
This happens because we incorrectly skip bus resources of
[mem 0x00000000-0xffffffff] because we think they are of size zero.
When resource_size_t is 32 bits wide, resource_size() on
[mem 0x00000000-0xffffffff] returns 0 because (r->end - r->start + 1)
overflows.
Therefore, we can't use "resource_size() == 0" to decide that allocation
from this resource will fail. allocate_resource() should fail anyway if it
can't satisfy the address constraints, so we should just depend on that.
A [mem 0x00000000-0xffffffff] bus resource is obviously not really valid,
but we do fall back to it as a default when we don't have information about
host bridge apertures.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=71611
Fixes: f75b99d5a77d PCI: Enforce bus address limits in resource allocation
Reported-and-tested-by: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions