Re: [PATCH] PCI: Do not touch siblings in pci_assign_unassigned_bridge_resources

From: Yinghai Lu
Date: Tue Jul 01 2014 - 14:36:03 EST


On Mon, Jun 30, 2014 at 3:47 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
>> Should not be dangerous, just second try.
>
> I still don't understand this. Why do we set "res->flags = 0"? That
> clears out the resource type. Where do we figure out the type of "res"
> again?

pci_bridge_check_ranges()

>> Subject: [PATCH] pci: Add back missing MEM_64 check for hotplug path
>>
>> We miss that in
>> | commit 5b28541552ef5eeffc41d6936105f38c2508e566
>> | PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources
>> for pci hotplug path.
>
> This changelog is useless. I don't have time to spend a few hours
> figuring out why we want this change.

We have MEM_64 in type_mask from pci_assign_unassigned_root_bus_resources().
And I missed the same change for hotplug path.


That is for exact type checking.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/