Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1231668
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. |
| Date | 2015-09-23 21:30 +0200 |
| Message-ID | <qbXTP-58R-3@gated-at.bofh.it> (permalink) |
| References | <q9Pxo-8wg-3@gated-at.bofh.it> <qbWEq-3q5-33@gated-at.bofh.it> <qbXTP-58R-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wednesday 23 September 2015 11:21:56 David Daney wrote: > >> > >> /* Limit the bus-range to fit within reg */ > >> - bus_max = pci->cfg.bus_range->start + > >> - (resource_size(&pci->cfg.res) >> pci->cfg.ops.bus_shift) - 1; > >> + bus_max = (resource_size(&pci->cfg.res) >> pci->cfg.ops.bus_shift) - 1; > >> + if (bus_max > 255) > >> + bus_max = 255; > > > > I still don't understand the need for this part. If the cfg space is bigger > > than bus_max, isn't that simply an invalid resource? Given that the resource > > could be broken in other ways too, this check feels more like a specific > > workaround rather than generally useful code. > > Imagine... > > bus-range [0x80 .. 0xff], this requires a cfg.res that will cover the > entire range of 0..0xff. > > according to the calculations above, (resource_size(&pci->cfg.res) >> > pci->cfg.ops.bus_shift) - 1 will have a value of 0xff, so... Extending the computation to 32 bit seems fine, but I'd rather warn loudly if the bus range does not fit within the registers. Also note that the computation is already correct with my interpretation of the reg property. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Will Deacon <will.deacon@arm.com> - 2015-09-23 20:10 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Arnd Bergmann <arnd@arndb.de> - 2015-09-23 21:30 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Arnd Bergmann <arnd@arndb.de> - 2015-09-23 21:40 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Will Deacon <will.deacon@arm.com> - 2015-09-23 21:50 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Arnd Bergmann <arnd@arndb.de> - 2015-09-23 22:50 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Will Deacon <will.deacon@arm.com> - 2015-09-23 21:40 +0200
Re: [PATCH v2 4/5] PCI: generic: Correct, and avoid overflow, in bus_max calculation. Will Deacon <will.deacon@arm.com> - 2015-09-23 21:40 +0200
csiph-web