* [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties @ 2013-09-17 18:38 Jason Gunthorpe 2013-09-17 19:05 ` Thomas Petazzoni 0 siblings, 1 reply; 4+ messages in thread From: Jason Gunthorpe @ 2013-09-17 18:38 UTC (permalink / raw) To: linux-arm-kernel If the property was not specified then then the returned resource had a resource_size(..) == 1, rather than 0. The PCI-E driver checks for 0 so it blindly continues on with a corrupted resource. Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> --- drivers/bus/mvebu-mbus.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c index 19ab6ff..7a66203 100644 --- a/drivers/bus/mvebu-mbus.c +++ b/drivers/bus/mvebu-mbus.c @@ -866,6 +866,8 @@ static void __init mvebu_mbus_get_pcie_resources(struct device_node *np, */ memset(mem, 0, sizeof(struct resource)); memset(io, 0, sizeof(struct resource)); + mem->end--; + io->end--; ret = of_property_read_u32_array(np, "pcie-mem-aperture", reg, ARRAY_SIZE(reg)); if (!ret) { -- 1.8.1.2 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties 2013-09-17 18:38 [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties Jason Gunthorpe @ 2013-09-17 19:05 ` Thomas Petazzoni 2013-09-17 19:13 ` Jason Gunthorpe 0 siblings, 1 reply; 4+ messages in thread From: Thomas Petazzoni @ 2013-09-17 19:05 UTC (permalink / raw) To: linux-arm-kernel Dear Jason Gunthorpe, On Tue, 17 Sep 2013 12:38:53 -0600, Jason Gunthorpe wrote: > If the property was not specified then then the returned resource > had a resource_size(..) == 1, rather than 0. The PCI-E driver checks > for 0 so it blindly continues on with a corrupted resource. > > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > --- > drivers/bus/mvebu-mbus.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c > index 19ab6ff..7a66203 100644 > --- a/drivers/bus/mvebu-mbus.c > +++ b/drivers/bus/mvebu-mbus.c > @@ -866,6 +866,8 @@ static void __init mvebu_mbus_get_pcie_resources(struct device_node *np, > */ > memset(mem, 0, sizeof(struct resource)); > memset(io, 0, sizeof(struct resource)); > + mem->end--; > + io->end--; > > ret = of_property_read_u32_array(np, "pcie-mem-aperture", reg, ARRAY_SIZE(reg)); > if (!ret) { This seems a little bit nasty, isn't it? Can't we instead teach the PCIe driver to be a little bit smarter when testing if those resources are valid or not? Thanks! Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties 2013-09-17 19:05 ` Thomas Petazzoni @ 2013-09-17 19:13 ` Jason Gunthorpe 2013-09-17 19:22 ` Thomas Petazzoni 0 siblings, 1 reply; 4+ messages in thread From: Jason Gunthorpe @ 2013-09-17 19:13 UTC (permalink / raw) To: linux-arm-kernel On Tue, Sep 17, 2013 at 09:05:03PM +0200, Thomas Petazzoni wrote: > Dear Jason Gunthorpe, > > On Tue, 17 Sep 2013 12:38:53 -0600, Jason Gunthorpe wrote: > > If the property was not specified then then the returned resource > > had a resource_size(..) == 1, rather than 0. The PCI-E driver checks > > for 0 so it blindly continues on with a corrupted resource. > > > > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > > drivers/bus/mvebu-mbus.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c > > index 19ab6ff..7a66203 100644 > > +++ b/drivers/bus/mvebu-mbus.c > > @@ -866,6 +866,8 @@ static void __init mvebu_mbus_get_pcie_resources(struct device_node *np, > > */ > > memset(mem, 0, sizeof(struct resource)); > > memset(io, 0, sizeof(struct resource)); > > + mem->end--; > > + io->end--; > > > > ret = of_property_read_u32_array(np, "pcie-mem-aperture", reg, ARRAY_SIZE(reg)); > > if (!ret) { > > This seems a little bit nasty, isn't it? Well, I'm not 100% sure, but AFAICT that is how struct resources should be used. The start/end address are inclusive, so the resource (start=0,end=0) describes 1 byte at address 0. The only way to get a 0 sized resource is (start=0,end=-1) Before I did this I checked other user of resource_size and found tests to zero, so the above seems to be correct.. Eg a quick grep shows: arch/powerpc/kernel/pci-common.c: pcibios_fixup_bridge if (pci_has_flag(PCI_REASSIGN_ALL_RSRC)) { res->flags |= IORESOURCE_UNSET; res->start = 0; res->end = -1; continue; } Do you see something different? Jason ^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties 2013-09-17 19:13 ` Jason Gunthorpe @ 2013-09-17 19:22 ` Thomas Petazzoni 0 siblings, 0 replies; 4+ messages in thread From: Thomas Petazzoni @ 2013-09-17 19:22 UTC (permalink / raw) To: linux-arm-kernel Dear Jason Gunthorpe, On Tue, 17 Sep 2013 13:13:42 -0600, Jason Gunthorpe wrote: > Well, I'm not 100% sure, but AFAICT that is how struct resources > should be used. The start/end address are inclusive, so the resource > (start=0,end=0) describes 1 byte at address 0. > > The only way to get a 0 sized resource is (start=0,end=-1) So in the ideal world, we would have a resource_init(&res) that would set start=0 and end=-1 or something like that. > Before I did this I checked other user of resource_size and found > tests to zero, so the above seems to be correct.. > > Eg a quick grep shows: > arch/powerpc/kernel/pci-common.c: pcibios_fixup_bridge > > if (pci_has_flag(PCI_REASSIGN_ALL_RSRC)) { > res->flags |= IORESOURCE_UNSET; > res->start = 0; > res->end = -1; > continue; > } > > Do you see something different? Well, apparently what you did is the commonly adopted way. Maybe just add a comment in the code above those two lines to explain what may seem a little strange initially? Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-09-17 19:22 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-09-17 18:38 [PATCH] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties Jason Gunthorpe 2013-09-17 19:05 ` Thomas Petazzoni 2013-09-17 19:13 ` Jason Gunthorpe 2013-09-17 19:22 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).