* [PATCH] pci: fix I/O space page leak
@ 2018-06-20 17:51 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-20 17:51 UTC (permalink / raw)
To: Bjorn Helgaas, linux-pci, Linus Walleij, Jingoo Han, Joao Pinto,
Lorenzo Pieralisi, Thomas Petazzoni, Rob Herring, Tanmay Inamdar,
Ryder Lee
Cc: Matthias Brugger, linux-arm-kernel, linux-mediatek, linux-renesas-soc
When testing the R-Car PCIe driver on the Condor board, I noticed that iff
I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
[ 1.225819] kernel BUG at lib/ioremap.c:72!
[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 1.235496] Modules linked in:
[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
[ 1.252075] Workqueue: events deferred_probe_work_func
[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
[ 1.271002] sp : ffff000008da39e0
[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
[ 1.361056] Call trace:
[ 1.363504] ioremap_page_range+0x370/0x3c8
[ 1.367695] pci_remap_iospace+0x7c/0xac
[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
[ 1.376945] rcar_pcie_probe+0x4c/0xb04
[ 1.380786] platform_drv_probe+0x50/0xbc
[ 1.384799] driver_probe_device+0x21c/0x308
[ 1.389072] __device_attach_driver+0x98/0xc8
[ 1.393431] bus_for_each_drv+0x54/0x94
[ 1.397269] __device_attach+0xc4/0x12c
[ 1.401107] device_initial_probe+0x10/0x18
[ 1.405292] bus_probe_device+0x90/0x98
[ 1.409130] deferred_probe_work_func+0xb0/0x150
[ 1.413756] process_one_work+0x12c/0x29c
[ 1.417768] worker_thread+0x200/0x3fc
[ 1.421522] kthread+0x108/0x134
[ 1.424755] ret_from_fork+0x10/0x18
[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
It turned out that pci_remap_iospace() wasn't undone when the driver's
probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
the probe was retried, finally causing the BUG due to trying to remap
already remapped pages.
The most feasible solution seems to introduce devm_pci_remap_iospace()
and call it instead of pci_remap_iospace(), so that the pages get unmapped
automagically on any probe failure.
And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
drivers that have probably copied the bad example...
Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: stable@vger.kernel.org
---
The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
It has only been tested with the R-Car PCIe driver...
drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
drivers/pci/controller/pci-aardvark.c | 2 -
drivers/pci/controller/pci-ftpci100.c | 2 -
drivers/pci/controller/pci-v3-semi.c | 2 -
drivers/pci/controller/pci-versatile.c | 2 -
drivers/pci/controller/pci-xgene.c | 2 -
drivers/pci/controller/pcie-mediatek.c | 2 -
drivers/pci/of.c | 2 -
drivers/pci/pci.c | 38 ++++++++++++++++++++++
include/linux/pci.h | 2 +
10 files changed, 49 insertions(+), 8 deletions(-)
Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
===================================================================
--- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
+++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
@@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
switch (resource_type(win->res)) {
case IORESOURCE_IO:
- ret = pci_remap_iospace(win->res, pp->io_base);
+ ret = devm_pci_remap_iospace(dev, win->res,
+ pp->io_base);
if (ret) {
dev_warn(dev, "Error %d: failed to map resource %pR\n",
ret, win->res);
Index: pci/drivers/pci/controller/pci-aardvark.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-aardvark.c
+++ pci/drivers/pci/controller/pci-aardvark.c
@@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
0, 0xF8000000, 0,
lower_32_bits(res->start),
OB_PCIE_IO);
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-ftpci100.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-ftpci100.c
+++ pci/drivers/pci/controller/pci-ftpci100.c
@@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
dev_err(dev, "illegal IO mem size\n");
return -EINVAL;
}
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
ret, io);
Index: pci/drivers/pci/controller/pci-v3-semi.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-v3-semi.c
+++ pci/drivers/pci/controller/pci-v3-semi.c
@@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
v3->io_bus_addr = io->start - win->offset;
dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
io, &v3->io_bus_addr);
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev,
"error %d: failed to map resource %pR\n",
Index: pci/drivers/pci/controller/pci-versatile.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-versatile.c
+++ pci/drivers/pci/controller/pci-versatile.c
@@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-xgene.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-xgene.c
+++ pci/drivers/pci/controller/pci-xgene.c
@@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
case IORESOURCE_IO:
xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
res->start - window->offset);
- ret = pci_remap_iospace(res, io_base);
+ ret = devm_pci_remap_iospace(dev, res, io_base);
if (ret < 0)
return ret;
break;
Index: pci/drivers/pci/controller/pcie-mediatek.c
===================================================================
--- pci.orig/drivers/pci/controller/pcie-mediatek.c
+++ pci/drivers/pci/controller/pcie-mediatek.c
@@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
if (err < 0)
return err;
- pci_remap_iospace(&pcie->pio, pcie->io.start);
+ devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
return 0;
}
Index: pci/drivers/pci/of.c
===================================================================
--- pci.orig/drivers/pci/of.c
+++ pci/drivers/pci/of.c
@@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/pci.c
===================================================================
--- pci.orig/drivers/pci/pci.c
+++ pci/drivers/pci/pci.c
@@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
}
EXPORT_SYMBOL(pci_unmap_iospace);
+static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
+{
+ struct resource **res = ptr;
+
+ pci_unmap_iospace(*res);
+}
+
+/**
+ * devm_pci_remap_iospace - Managed pci_remap_iospace()
+ * @dev: Generic device to remap IO address for
+ * @res: Resource describing the I/O space
+ * @phys_addr: physical address of range to be mapped
+ *
+ * Managed pci_remap_iospace(). Map is automatically unmapped on driver
+ * detach.
+ */
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr)
+{
+ const struct resource **ptr;
+ int error;
+
+ ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
+ if (!ptr)
+ return -ENOMEM;
+
+ error = pci_remap_iospace(res, phys_addr);
+ if (error) {
+ devres_free(ptr);
+ } else {
+ *ptr = res;
+ devres_add(dev, ptr);
+ }
+
+ return error;
+}
+EXPORT_SYMBOL(devm_pci_remap_iospace);
+
/**
* devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
* @dev: Generic device to remap IO address for
Index: pci/include/linux/pci.h
===================================================================
--- pci.orig/include/linux/pci.h
+++ pci/include/linux/pci.h
@@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
unsigned long pci_address_to_pio(phys_addr_t addr);
phys_addr_t pci_pio_to_address(unsigned long pio);
int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr);
void pci_unmap_iospace(struct resource *res);
void __iomem *devm_pci_remap_cfgspace(struct device *dev,
resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-20 17:51 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-20 17:51 UTC (permalink / raw)
To: Bjorn Helgaas, linux-pci-u79uwXL29TY76Z2rM5mHXA, Linus Walleij,
Jingoo Han, Joao Pinto, Lorenzo Pieralisi, Thomas Petazzoni,
Rob Herring, Tanmay Inamdar, Ryder Lee
Cc: Matthias Brugger, linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
When testing the R-Car PCIe driver on the Condor board, I noticed that iff
I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
[ 1.225819] kernel BUG at lib/ioremap.c:72!
[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 1.235496] Modules linked in:
[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
[ 1.252075] Workqueue: events deferred_probe_work_func
[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
[ 1.271002] sp : ffff000008da39e0
[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
[ 1.361056] Call trace:
[ 1.363504] ioremap_page_range+0x370/0x3c8
[ 1.367695] pci_remap_iospace+0x7c/0xac
[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
[ 1.376945] rcar_pcie_probe+0x4c/0xb04
[ 1.380786] platform_drv_probe+0x50/0xbc
[ 1.384799] driver_probe_device+0x21c/0x308
[ 1.389072] __device_attach_driver+0x98/0xc8
[ 1.393431] bus_for_each_drv+0x54/0x94
[ 1.397269] __device_attach+0xc4/0x12c
[ 1.401107] device_initial_probe+0x10/0x18
[ 1.405292] bus_probe_device+0x90/0x98
[ 1.409130] deferred_probe_work_func+0xb0/0x150
[ 1.413756] process_one_work+0x12c/0x29c
[ 1.417768] worker_thread+0x200/0x3fc
[ 1.421522] kthread+0x108/0x134
[ 1.424755] ret_from_fork+0x10/0x18
[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
It turned out that pci_remap_iospace() wasn't undone when the driver's
probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
the probe was retried, finally causing the BUG due to trying to remap
already remapped pages.
The most feasible solution seems to introduce devm_pci_remap_iospace()
and call it instead of pci_remap_iospace(), so that the pages get unmapped
automagically on any probe failure.
And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
drivers that have probably copied the bad example...
Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
Signed-off-by: Sergei Shtylyov <sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
---
The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
It has only been tested with the R-Car PCIe driver...
drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
drivers/pci/controller/pci-aardvark.c | 2 -
drivers/pci/controller/pci-ftpci100.c | 2 -
drivers/pci/controller/pci-v3-semi.c | 2 -
drivers/pci/controller/pci-versatile.c | 2 -
drivers/pci/controller/pci-xgene.c | 2 -
drivers/pci/controller/pcie-mediatek.c | 2 -
drivers/pci/of.c | 2 -
drivers/pci/pci.c | 38 ++++++++++++++++++++++
include/linux/pci.h | 2 +
10 files changed, 49 insertions(+), 8 deletions(-)
Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
===================================================================
--- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
+++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
@@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
switch (resource_type(win->res)) {
case IORESOURCE_IO:
- ret = pci_remap_iospace(win->res, pp->io_base);
+ ret = devm_pci_remap_iospace(dev, win->res,
+ pp->io_base);
if (ret) {
dev_warn(dev, "Error %d: failed to map resource %pR\n",
ret, win->res);
Index: pci/drivers/pci/controller/pci-aardvark.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-aardvark.c
+++ pci/drivers/pci/controller/pci-aardvark.c
@@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
0, 0xF8000000, 0,
lower_32_bits(res->start),
OB_PCIE_IO);
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-ftpci100.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-ftpci100.c
+++ pci/drivers/pci/controller/pci-ftpci100.c
@@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
dev_err(dev, "illegal IO mem size\n");
return -EINVAL;
}
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
ret, io);
Index: pci/drivers/pci/controller/pci-v3-semi.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-v3-semi.c
+++ pci/drivers/pci/controller/pci-v3-semi.c
@@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
v3->io_bus_addr = io->start - win->offset;
dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
io, &v3->io_bus_addr);
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev,
"error %d: failed to map resource %pR\n",
Index: pci/drivers/pci/controller/pci-versatile.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-versatile.c
+++ pci/drivers/pci/controller/pci-versatile.c
@@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-xgene.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-xgene.c
+++ pci/drivers/pci/controller/pci-xgene.c
@@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
case IORESOURCE_IO:
xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
res->start - window->offset);
- ret = pci_remap_iospace(res, io_base);
+ ret = devm_pci_remap_iospace(dev, res, io_base);
if (ret < 0)
return ret;
break;
Index: pci/drivers/pci/controller/pcie-mediatek.c
===================================================================
--- pci.orig/drivers/pci/controller/pcie-mediatek.c
+++ pci/drivers/pci/controller/pcie-mediatek.c
@@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
if (err < 0)
return err;
- pci_remap_iospace(&pcie->pio, pcie->io.start);
+ devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
return 0;
}
Index: pci/drivers/pci/of.c
===================================================================
--- pci.orig/drivers/pci/of.c
+++ pci/drivers/pci/of.c
@@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/pci.c
===================================================================
--- pci.orig/drivers/pci/pci.c
+++ pci/drivers/pci/pci.c
@@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
}
EXPORT_SYMBOL(pci_unmap_iospace);
+static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
+{
+ struct resource **res = ptr;
+
+ pci_unmap_iospace(*res);
+}
+
+/**
+ * devm_pci_remap_iospace - Managed pci_remap_iospace()
+ * @dev: Generic device to remap IO address for
+ * @res: Resource describing the I/O space
+ * @phys_addr: physical address of range to be mapped
+ *
+ * Managed pci_remap_iospace(). Map is automatically unmapped on driver
+ * detach.
+ */
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr)
+{
+ const struct resource **ptr;
+ int error;
+
+ ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
+ if (!ptr)
+ return -ENOMEM;
+
+ error = pci_remap_iospace(res, phys_addr);
+ if (error) {
+ devres_free(ptr);
+ } else {
+ *ptr = res;
+ devres_add(dev, ptr);
+ }
+
+ return error;
+}
+EXPORT_SYMBOL(devm_pci_remap_iospace);
+
/**
* devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
* @dev: Generic device to remap IO address for
Index: pci/include/linux/pci.h
===================================================================
--- pci.orig/include/linux/pci.h
+++ pci/include/linux/pci.h
@@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
unsigned long pci_address_to_pio(phys_addr_t addr);
phys_addr_t pci_pio_to_address(unsigned long pio);
int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr);
void pci_unmap_iospace(struct resource *res);
void __iomem *devm_pci_remap_cfgspace(struct device *dev,
resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-20 17:51 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-20 17:51 UTC (permalink / raw)
To: linux-arm-kernel
When testing the R-Car PCIe driver on the Condor board, I noticed that iff
I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
[ 1.225819] kernel BUG at lib/ioremap.c:72!
[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 1.235496] Modules linked in:
[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
[ 1.252075] Workqueue: events deferred_probe_work_func
[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
[ 1.271002] sp : ffff000008da39e0
[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
[ 1.361056] Call trace:
[ 1.363504] ioremap_page_range+0x370/0x3c8
[ 1.367695] pci_remap_iospace+0x7c/0xac
[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
[ 1.376945] rcar_pcie_probe+0x4c/0xb04
[ 1.380786] platform_drv_probe+0x50/0xbc
[ 1.384799] driver_probe_device+0x21c/0x308
[ 1.389072] __device_attach_driver+0x98/0xc8
[ 1.393431] bus_for_each_drv+0x54/0x94
[ 1.397269] __device_attach+0xc4/0x12c
[ 1.401107] device_initial_probe+0x10/0x18
[ 1.405292] bus_probe_device+0x90/0x98
[ 1.409130] deferred_probe_work_func+0xb0/0x150
[ 1.413756] process_one_work+0x12c/0x29c
[ 1.417768] worker_thread+0x200/0x3fc
[ 1.421522] kthread+0x108/0x134
[ 1.424755] ret_from_fork+0x10/0x18
[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
It turned out that pci_remap_iospace() wasn't undone when the driver's
probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
the probe was retried, finally causing the BUG due to trying to remap
already remapped pages.
The most feasible solution seems to introduce devm_pci_remap_iospace()
and call it instead of pci_remap_iospace(), so that the pages get unmapped
automagically on any probe failure.
And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
drivers that have probably copied the bad example...
Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: stable at vger.kernel.org
---
The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
It has only been tested with the R-Car PCIe driver...
drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
drivers/pci/controller/pci-aardvark.c | 2 -
drivers/pci/controller/pci-ftpci100.c | 2 -
drivers/pci/controller/pci-v3-semi.c | 2 -
drivers/pci/controller/pci-versatile.c | 2 -
drivers/pci/controller/pci-xgene.c | 2 -
drivers/pci/controller/pcie-mediatek.c | 2 -
drivers/pci/of.c | 2 -
drivers/pci/pci.c | 38 ++++++++++++++++++++++
include/linux/pci.h | 2 +
10 files changed, 49 insertions(+), 8 deletions(-)
Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
===================================================================
--- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
+++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
@@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
switch (resource_type(win->res)) {
case IORESOURCE_IO:
- ret = pci_remap_iospace(win->res, pp->io_base);
+ ret = devm_pci_remap_iospace(dev, win->res,
+ pp->io_base);
if (ret) {
dev_warn(dev, "Error %d: failed to map resource %pR\n",
ret, win->res);
Index: pci/drivers/pci/controller/pci-aardvark.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-aardvark.c
+++ pci/drivers/pci/controller/pci-aardvark.c
@@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
0, 0xF8000000, 0,
lower_32_bits(res->start),
OB_PCIE_IO);
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-ftpci100.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-ftpci100.c
+++ pci/drivers/pci/controller/pci-ftpci100.c
@@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
dev_err(dev, "illegal IO mem size\n");
return -EINVAL;
}
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
ret, io);
Index: pci/drivers/pci/controller/pci-v3-semi.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-v3-semi.c
+++ pci/drivers/pci/controller/pci-v3-semi.c
@@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
v3->io_bus_addr = io->start - win->offset;
dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
io, &v3->io_bus_addr);
- ret = pci_remap_iospace(io, io_base);
+ ret = devm_pci_remap_iospace(dev, io, io_base);
if (ret) {
dev_warn(dev,
"error %d: failed to map resource %pR\n",
Index: pci/drivers/pci/controller/pci-versatile.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-versatile.c
+++ pci/drivers/pci/controller/pci-versatile.c
@@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/controller/pci-xgene.c
===================================================================
--- pci.orig/drivers/pci/controller/pci-xgene.c
+++ pci/drivers/pci/controller/pci-xgene.c
@@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
case IORESOURCE_IO:
xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
res->start - window->offset);
- ret = pci_remap_iospace(res, io_base);
+ ret = devm_pci_remap_iospace(dev, res, io_base);
if (ret < 0)
return ret;
break;
Index: pci/drivers/pci/controller/pcie-mediatek.c
===================================================================
--- pci.orig/drivers/pci/controller/pcie-mediatek.c
+++ pci/drivers/pci/controller/pcie-mediatek.c
@@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
if (err < 0)
return err;
- pci_remap_iospace(&pcie->pio, pcie->io.start);
+ devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
return 0;
}
Index: pci/drivers/pci/of.c
===================================================================
--- pci.orig/drivers/pci/of.c
+++ pci/drivers/pci/of.c
@@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
switch (resource_type(res)) {
case IORESOURCE_IO:
- err = pci_remap_iospace(res, iobase);
+ err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
Index: pci/drivers/pci/pci.c
===================================================================
--- pci.orig/drivers/pci/pci.c
+++ pci/drivers/pci/pci.c
@@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
}
EXPORT_SYMBOL(pci_unmap_iospace);
+static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
+{
+ struct resource **res = ptr;
+
+ pci_unmap_iospace(*res);
+}
+
+/**
+ * devm_pci_remap_iospace - Managed pci_remap_iospace()
+ * @dev: Generic device to remap IO address for
+ * @res: Resource describing the I/O space
+ * @phys_addr: physical address of range to be mapped
+ *
+ * Managed pci_remap_iospace(). Map is automatically unmapped on driver
+ * detach.
+ */
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr)
+{
+ const struct resource **ptr;
+ int error;
+
+ ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
+ if (!ptr)
+ return -ENOMEM;
+
+ error = pci_remap_iospace(res, phys_addr);
+ if (error) {
+ devres_free(ptr);
+ } else {
+ *ptr = res;
+ devres_add(dev, ptr);
+ }
+
+ return error;
+}
+EXPORT_SYMBOL(devm_pci_remap_iospace);
+
/**
* devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
* @dev: Generic device to remap IO address for
Index: pci/include/linux/pci.h
===================================================================
--- pci.orig/include/linux/pci.h
+++ pci/include/linux/pci.h
@@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
unsigned long pci_address_to_pio(phys_addr_t addr);
phys_addr_t pci_pio_to_address(unsigned long pio);
int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
+int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
+ phys_addr_t phys_addr);
void pci_unmap_iospace(struct resource *res);
void __iomem *devm_pci_remap_cfgspace(struct device *dev,
resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-20 17:51 ` Sergei Shtylyov
(?)
(?)
@ 2018-06-20 19:36 ` Jingoo Han
-1 siblings, 0 replies; 37+ messages in thread
From: Jingoo Han @ 2018-06-20 19:36 UTC (permalink / raw)
To: 'Sergei Shtylyov', 'Bjorn Helgaas',
linux-pci, 'Linus Walleij', 'Joao Pinto',
'Lorenzo Pieralisi', 'Thomas Petazzoni',
'Rob Herring', 'Tanmay Inamdar',
'Ryder Lee'
Cc: 'Matthias Brugger',
linux-arm-kernel, linux-mediatek, linux-renesas-soc
On Wednesday, June 20, 2018 1:52 PM, Sergei Shtylyov wrote:
>
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty
> #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x
> (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use
> by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller
> driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI
> Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe
> host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller
> support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
It looks good!
For drivers/pci/controller/dwc/pcie-designware-host.c,
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git'
> repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map
> resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr),
> GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-20 19:36 ` Jingoo Han
0 siblings, 0 replies; 37+ messages in thread
From: Jingoo Han @ 2018-06-20 19:36 UTC (permalink / raw)
To: 'Sergei Shtylyov', 'Bjorn Helgaas',
linux-pci, 'Linus Walleij', 'Joao Pinto',
'Lorenzo Pieralisi', 'Thomas Petazzoni',
'Rob Herring', 'Tanmay Inamdar',
'Ryder Lee'
Cc: 'Matthias Brugger',
linux-renesas-soc, linux-mediatek, linux-arm-kernel
On Wednesday, June 20, 2018 1:52 PM, Sergei Shtylyov wrote:
>
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty
> #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x
> (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use
> by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller
> driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI
> Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe
> host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller
> support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
It looks good!
For drivers/pci/controller/dwc/pcie-designware-host.c,
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git'
> repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map
> resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr),
> GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-20 19:36 ` Jingoo Han
0 siblings, 0 replies; 37+ messages in thread
From: Jingoo Han @ 2018-06-20 19:36 UTC (permalink / raw)
To: 'Sergei Shtylyov', 'Bjorn Helgaas',
linux-pci, 'Linus Walleij', 'Joao Pinto',
'Lorenzo Pieralisi', 'Thomas Petazzoni',
'Rob Herring', 'Tanmay Inamdar',
'Ryder Lee'
Cc: 'Matthias Brugger',
linux-renesas-soc, linux-mediatek, linux-arm-kernel
On Wednesday, June 20, 2018 1:52 PM, Sergei Shtylyov wrote:
>
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty
> #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x
> (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use
> by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller
> driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI
> Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe
> host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller
> support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
It looks good!
For drivers/pci/controller/dwc/pcie-designware-host.c,
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git'
> repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map
> resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr),
> GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-20 19:36 ` Jingoo Han
0 siblings, 0 replies; 37+ messages in thread
From: Jingoo Han @ 2018-06-20 19:36 UTC (permalink / raw)
To: linux-arm-kernel
On Wednesday, June 20, 2018 1:52 PM, Sergei Shtylyov wrote:
>
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty
> #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x
> (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use
> by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller
> driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI
> Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe
> host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller
> support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable at vger.kernel.org
It looks good!
For drivers/pci/controller/dwc/pcie-designware-host.c,
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git'
> repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map
> resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map
> resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr),
> GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-20 17:51 ` Sergei Shtylyov
(?)
(?)
@ 2018-06-21 6:55 ` Thomas Petazzoni
-1 siblings, 0 replies; 37+ messages in thread
From: Thomas Petazzoni @ 2018-06-21 6:55 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Bjorn Helgaas, linux-pci, Linus Walleij, Jingoo Han, Joao Pinto,
Lorenzo Pieralisi, Thomas Petazzoni, Rob Herring, Tanmay Inamdar,
Ryder Lee, Matthias Brugger, linux-arm-kernel, linux-mediatek,
linux-renesas-soc
Hello,
On Wed, 20 Jun 2018 20:51:37 +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
For the Aardvark chunk:
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-21 6:55 ` Thomas Petazzoni
0 siblings, 0 replies; 37+ messages in thread
From: Thomas Petazzoni @ 2018-06-21 6:55 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, Ryder Lee, linux-renesas-soc, Matthias Brugger,
Lorenzo Pieralisi, linux-mediatek, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-arm-kernel
Hello,
On Wed, 20 Jun 2018 20:51:37 +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
For the Aardvark chunk:
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-21 6:55 ` Thomas Petazzoni
0 siblings, 0 replies; 37+ messages in thread
From: Thomas Petazzoni @ 2018-06-21 6:55 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, Ryder Lee, linux-renesas-soc, Matthias Brugger,
Lorenzo Pieralisi, linux-mediatek, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-arm-kernel
Hello,
On Wed, 20 Jun 2018 20:51:37 +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
For the Aardvark chunk:
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-21 6:55 ` Thomas Petazzoni
0 siblings, 0 replies; 37+ messages in thread
From: Thomas Petazzoni @ 2018-06-21 6:55 UTC (permalink / raw)
To: linux-arm-kernel
Hello,
On Wed, 20 Jun 2018 20:51:37 +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable at vger.kernel.org
>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
For the Aardvark chunk:
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-20 17:51 ` Sergei Shtylyov
(?)
(?)
@ 2018-06-26 7:36 ` Linus Walleij
-1 siblings, 0 replies; 37+ messages in thread
From: Linus Walleij @ 2018-06-26 7:36 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Bjorn Helgaas, linux-pci, Jingoo Han, Joao Pinto,
Lorenzo Pieralisi, Thomas Petazzoni, Rob Herring, Tanmay Inamdar,
Ryder Lee, Matthias Brugger, Linux ARM,
moderated list:ARM/Mediatek SoC support, Linux-Renesas
On Wed, Jun 20, 2018 at 7:51 PM Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Nice, clean and thorough fix!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-26 7:36 ` Linus Walleij
0 siblings, 0 replies; 37+ messages in thread
From: Linus Walleij @ 2018-06-26 7:36 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci, Ryder Lee,
Linux-Renesas, Matthias Brugger, Lorenzo Pieralisi,
moderated list:ARM/Mediatek SoC support, Tanmay Inamdar,
Jingoo Han, Bjorn Helgaas, Linux ARM
On Wed, Jun 20, 2018 at 7:51 PM Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Nice, clean and thorough fix!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-26 7:36 ` Linus Walleij
0 siblings, 0 replies; 37+ messages in thread
From: Linus Walleij @ 2018-06-26 7:36 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci, Ryder Lee,
Linux-Renesas, Matthias Brugger, Lorenzo Pieralisi,
moderated list:ARM/Mediatek SoC support, Tanmay Inamdar,
Jingoo Han, Bjorn Helgaas, Linux ARM
On Wed, Jun 20, 2018 at 7:51 PM Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Nice, clean and thorough fix!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-26 7:36 ` Linus Walleij
0 siblings, 0 replies; 37+ messages in thread
From: Linus Walleij @ 2018-06-26 7:36 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jun 20, 2018 at 7:51 PM Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable at vger.kernel.org
Nice, clean and thorough fix!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-20 17:51 ` Sergei Shtylyov
(?)
(?)
@ 2018-06-28 13:22 ` Bjorn Helgaas
-1 siblings, 0 replies; 37+ messages in thread
From: Bjorn Helgaas @ 2018-06-28 13:22 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Bjorn Helgaas, linux-pci, Linus Walleij, Jingoo Han, Joao Pinto,
Lorenzo Pieralisi, Thomas Petazzoni, Rob Herring, Tanmay Inamdar,
Ryder Lee, Matthias Brugger, linux-arm-kernel, linux-mediatek,
linux-renesas-soc
On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Let me know if you want me to take this, Lorenzo, otherwise:
s/pci: fix/PCI: Fix/ and
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-28 13:22 ` Bjorn Helgaas
0 siblings, 0 replies; 37+ messages in thread
From: Bjorn Helgaas @ 2018-06-28 13:22 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, Ryder Lee, linux-renesas-soc, Matthias Brugger,
Lorenzo Pieralisi, linux-mediatek, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-arm-kernel
On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Let me know if you want me to take this, Lorenzo, otherwise:
s/pci: fix/PCI: Fix/ and
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-28 13:22 ` Bjorn Helgaas
0 siblings, 0 replies; 37+ messages in thread
From: Bjorn Helgaas @ 2018-06-28 13:22 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, Ryder Lee, linux-renesas-soc, Matthias Brugger,
Lorenzo Pieralisi, linux-mediatek, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-arm-kernel
On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org
Let me know if you want me to take this, Lorenzo, otherwise:
s/pci: fix/PCI: Fix/ and
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-28 13:22 ` Bjorn Helgaas
0 siblings, 0 replies; 37+ messages in thread
From: Bjorn Helgaas @ 2018-06-28 13:22 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>
> [ 1.225819] kernel BUG at lib/ioremap.c:72!
> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> [ 1.235496] Modules linked in:
> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> [ 1.252075] Workqueue: events deferred_probe_work_func
> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> [ 1.271002] sp : ffff000008da39e0
> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> [ 1.361056] Call trace:
> [ 1.363504] ioremap_page_range+0x370/0x3c8
> [ 1.367695] pci_remap_iospace+0x7c/0xac
> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> [ 1.380786] platform_drv_probe+0x50/0xbc
> [ 1.384799] driver_probe_device+0x21c/0x308
> [ 1.389072] __device_attach_driver+0x98/0xc8
> [ 1.393431] bus_for_each_drv+0x54/0x94
> [ 1.397269] __device_attach+0xc4/0x12c
> [ 1.401107] device_initial_probe+0x10/0x18
> [ 1.405292] bus_probe_device+0x90/0x98
> [ 1.409130] deferred_probe_work_func+0xb0/0x150
> [ 1.413756] process_one_work+0x12c/0x29c
> [ 1.417768] worker_thread+0x200/0x3fc
> [ 1.421522] kthread+0x108/0x134
> [ 1.424755] ret_from_fork+0x10/0x18
> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>
> It turned out that pci_remap_iospace() wasn't undone when the driver's
> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> the probe was retried, finally causing the BUG due to trying to remap
> already remapped pages.
>
> The most feasible solution seems to introduce devm_pci_remap_iospace()
> and call it instead of pci_remap_iospace(), so that the pages get unmapped
> automagically on any probe failure.
>
> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> drivers that have probably copied the bad example...
>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable at vger.kernel.org
Let me know if you want me to take this, Lorenzo, otherwise:
s/pci: fix/PCI: Fix/ and
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> It has only been tested with the R-Car PCIe driver...
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> drivers/pci/controller/pci-aardvark.c | 2 -
> drivers/pci/controller/pci-ftpci100.c | 2 -
> drivers/pci/controller/pci-v3-semi.c | 2 -
> drivers/pci/controller/pci-versatile.c | 2 -
> drivers/pci/controller/pci-xgene.c | 2 -
> drivers/pci/controller/pcie-mediatek.c | 2 -
> drivers/pci/of.c | 2 -
> drivers/pci/pci.c | 38 ++++++++++++++++++++++
> include/linux/pci.h | 2 +
> 10 files changed, 49 insertions(+), 8 deletions(-)
>
> Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> switch (resource_type(win->res)) {
> case IORESOURCE_IO:
> - ret = pci_remap_iospace(win->res, pp->io_base);
> + ret = devm_pci_remap_iospace(dev, win->res,
> + pp->io_base);
> if (ret) {
> dev_warn(dev, "Error %d: failed to map resource %pR\n",
> ret, win->res);
> Index: pci/drivers/pci/controller/pci-aardvark.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-aardvark.c
> +++ pci/drivers/pci/controller/pci-aardvark.c
> @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> 0, 0xF8000000, 0,
> lower_32_bits(res->start),
> OB_PCIE_IO);
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-ftpci100.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> +++ pci/drivers/pci/controller/pci-ftpci100.c
> @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> dev_err(dev, "illegal IO mem size\n");
> return -EINVAL;
> }
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> ret, io);
> Index: pci/drivers/pci/controller/pci-v3-semi.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> +++ pci/drivers/pci/controller/pci-v3-semi.c
> @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> v3->io_bus_addr = io->start - win->offset;
> dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> io, &v3->io_bus_addr);
> - ret = pci_remap_iospace(io, io_base);
> + ret = devm_pci_remap_iospace(dev, io, io_base);
> if (ret) {
> dev_warn(dev,
> "error %d: failed to map resource %pR\n",
> Index: pci/drivers/pci/controller/pci-versatile.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-versatile.c
> +++ pci/drivers/pci/controller/pci-versatile.c
> @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/controller/pci-xgene.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pci-xgene.c
> +++ pci/drivers/pci/controller/pci-xgene.c
> @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> case IORESOURCE_IO:
> xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> res->start - window->offset);
> - ret = pci_remap_iospace(res, io_base);
> + ret = devm_pci_remap_iospace(dev, res, io_base);
> if (ret < 0)
> return ret;
> break;
> Index: pci/drivers/pci/controller/pcie-mediatek.c
> ===================================================================
> --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> +++ pci/drivers/pci/controller/pcie-mediatek.c
> @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> if (err < 0)
> return err;
>
> - pci_remap_iospace(&pcie->pio, pcie->io.start);
> + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
>
> return 0;
> }
> Index: pci/drivers/pci/of.c
> ===================================================================
> --- pci.orig/drivers/pci/of.c
> +++ pci/drivers/pci/of.c
> @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
>
> switch (resource_type(res)) {
> case IORESOURCE_IO:
> - err = pci_remap_iospace(res, iobase);
> + err = devm_pci_remap_iospace(dev, res, iobase);
> if (err) {
> dev_warn(dev, "error %d: failed to map resource %pR\n",
> err, res);
> Index: pci/drivers/pci/pci.c
> ===================================================================
> --- pci.orig/drivers/pci/pci.c
> +++ pci/drivers/pci/pci.c
> @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> }
> EXPORT_SYMBOL(pci_unmap_iospace);
>
> +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> +{
> + struct resource **res = ptr;
> +
> + pci_unmap_iospace(*res);
> +}
> +
> +/**
> + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> + * @dev: Generic device to remap IO address for
> + * @res: Resource describing the I/O space
> + * @phys_addr: physical address of range to be mapped
> + *
> + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> + * detach.
> + */
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr)
> +{
> + const struct resource **ptr;
> + int error;
> +
> + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> + error = pci_remap_iospace(res, phys_addr);
> + if (error) {
> + devres_free(ptr);
> + } else {
> + *ptr = res;
> + devres_add(dev, ptr);
> + }
> +
> + return error;
> +}
> +EXPORT_SYMBOL(devm_pci_remap_iospace);
> +
> /**
> * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> * @dev: Generic device to remap IO address for
> Index: pci/include/linux/pci.h
> ===================================================================
> --- pci.orig/include/linux/pci.h
> +++ pci/include/linux/pci.h
> @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> unsigned long pci_address_to_pio(phys_addr_t addr);
> phys_addr_t pci_pio_to_address(unsigned long pio);
> int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> + phys_addr_t phys_addr);
> void pci_unmap_iospace(struct resource *res);
> void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-28 13:22 ` Bjorn Helgaas
(?)
@ 2018-06-28 14:26 ` Lorenzo Pieralisi
-1 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-06-28 14:26 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Sergei Shtylyov, Bjorn Helgaas, linux-pci, Linus Walleij,
Jingoo Han, Joao Pinto, Thomas Petazzoni, Rob Herring,
Tanmay Inamdar, Ryder Lee, Matthias Brugger, linux-arm-kernel,
linux-mediatek, linux-renesas-soc
On Thu, Jun 28, 2018 at 08:22:59AM -0500, Bjorn Helgaas wrote:
> On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> > When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >
> > [ 1.225819] kernel BUG at lib/ioremap.c:72!
> > [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> > [ 1.235496] Modules linked in:
> > [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> > [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> > [ 1.252075] Workqueue: events deferred_probe_work_func
> > [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> > [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> > [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> > [ 1.271002] sp : ffff000008da39e0
> > [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> > [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> > [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> > [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> > [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> > [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> > [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> > [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> > [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> > [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> > [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> > [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> > [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> > [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> > [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> > [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> > [ 1.361056] Call trace:
> > [ 1.363504] ioremap_page_range+0x370/0x3c8
> > [ 1.367695] pci_remap_iospace+0x7c/0xac
> > [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> > [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> > [ 1.380786] platform_drv_probe+0x50/0xbc
> > [ 1.384799] driver_probe_device+0x21c/0x308
> > [ 1.389072] __device_attach_driver+0x98/0xc8
> > [ 1.393431] bus_for_each_drv+0x54/0x94
> > [ 1.397269] __device_attach+0xc4/0x12c
> > [ 1.401107] device_initial_probe+0x10/0x18
> > [ 1.405292] bus_probe_device+0x90/0x98
> > [ 1.409130] deferred_probe_work_func+0xb0/0x150
> > [ 1.413756] process_one_work+0x12c/0x29c
> > [ 1.417768] worker_thread+0x200/0x3fc
> > [ 1.421522] kthread+0x108/0x134
> > [ 1.424755] ret_from_fork+0x10/0x18
> > [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >
> > It turned out that pci_remap_iospace() wasn't undone when the driver's
> > probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > the probe was retried, finally causing the BUG due to trying to remap
> > already remapped pages.
> >
> > The most feasible solution seems to introduce devm_pci_remap_iospace()
> > and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > automagically on any probe failure.
> >
> > And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > drivers that have probably copied the bad example...
> >
> > Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > Cc: stable@vger.kernel.org
>
> Let me know if you want me to take this, Lorenzo, otherwise:
> s/pci: fix/PCI: Fix/ and
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
more so given the stable tag (and I think that each "Fixes" tag should
be self-contained), merging it as-is would give Greg (and us) a
headache when it comes to backporting it.
Honestly I think it is best to split it up and send it for v4.19 but
I am happy to hear other options.
Lorenzo
> > ---
> > The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> > It has only been tested with the R-Car PCIe driver...
> >
> > drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> > drivers/pci/controller/pci-aardvark.c | 2 -
> > drivers/pci/controller/pci-ftpci100.c | 2 -
> > drivers/pci/controller/pci-v3-semi.c | 2 -
> > drivers/pci/controller/pci-versatile.c | 2 -
> > drivers/pci/controller/pci-xgene.c | 2 -
> > drivers/pci/controller/pcie-mediatek.c | 2 -
> > drivers/pci/of.c | 2 -
> > drivers/pci/pci.c | 38 ++++++++++++++++++++++
> > include/linux/pci.h | 2 +
> > 10 files changed, 49 insertions(+), 8 deletions(-)
> >
> > Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> > +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> > resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> > switch (resource_type(win->res)) {
> > case IORESOURCE_IO:
> > - ret = pci_remap_iospace(win->res, pp->io_base);
> > + ret = devm_pci_remap_iospace(dev, win->res,
> > + pp->io_base);
> > if (ret) {
> > dev_warn(dev, "Error %d: failed to map resource %pR\n",
> > ret, win->res);
> > Index: pci/drivers/pci/controller/pci-aardvark.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-aardvark.c
> > +++ pci/drivers/pci/controller/pci-aardvark.c
> > @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> > 0, 0xF8000000, 0,
> > lower_32_bits(res->start),
> > OB_PCIE_IO);
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-ftpci100.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> > +++ pci/drivers/pci/controller/pci-ftpci100.c
> > @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> > dev_err(dev, "illegal IO mem size\n");
> > return -EINVAL;
> > }
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > ret, io);
> > Index: pci/drivers/pci/controller/pci-v3-semi.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> > +++ pci/drivers/pci/controller/pci-v3-semi.c
> > @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> > v3->io_bus_addr = io->start - win->offset;
> > dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> > io, &v3->io_bus_addr);
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev,
> > "error %d: failed to map resource %pR\n",
> > Index: pci/drivers/pci/controller/pci-versatile.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-versatile.c
> > +++ pci/drivers/pci/controller/pci-versatile.c
> > @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-xgene.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-xgene.c
> > +++ pci/drivers/pci/controller/pci-xgene.c
> > @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> > case IORESOURCE_IO:
> > xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> > res->start - window->offset);
> > - ret = pci_remap_iospace(res, io_base);
> > + ret = devm_pci_remap_iospace(dev, res, io_base);
> > if (ret < 0)
> > return ret;
> > break;
> > Index: pci/drivers/pci/controller/pcie-mediatek.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> > +++ pci/drivers/pci/controller/pcie-mediatek.c
> > @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> > if (err < 0)
> > return err;
> >
> > - pci_remap_iospace(&pcie->pio, pcie->io.start);
> > + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
> >
> > return 0;
> > }
> > Index: pci/drivers/pci/of.c
> > ===================================================================
> > --- pci.orig/drivers/pci/of.c
> > +++ pci/drivers/pci/of.c
> > @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/pci.c
> > ===================================================================
> > --- pci.orig/drivers/pci/pci.c
> > +++ pci/drivers/pci/pci.c
> > @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> > }
> > EXPORT_SYMBOL(pci_unmap_iospace);
> >
> > +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> > +{
> > + struct resource **res = ptr;
> > +
> > + pci_unmap_iospace(*res);
> > +}
> > +
> > +/**
> > + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> > + * @dev: Generic device to remap IO address for
> > + * @res: Resource describing the I/O space
> > + * @phys_addr: physical address of range to be mapped
> > + *
> > + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> > + * detach.
> > + */
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr)
> > +{
> > + const struct resource **ptr;
> > + int error;
> > +
> > + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> > + if (!ptr)
> > + return -ENOMEM;
> > +
> > + error = pci_remap_iospace(res, phys_addr);
> > + if (error) {
> > + devres_free(ptr);
> > + } else {
> > + *ptr = res;
> > + devres_add(dev, ptr);
> > + }
> > +
> > + return error;
> > +}
> > +EXPORT_SYMBOL(devm_pci_remap_iospace);
> > +
> > /**
> > * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> > * @dev: Generic device to remap IO address for
> > Index: pci/include/linux/pci.h
> > ===================================================================
> > --- pci.orig/include/linux/pci.h
> > +++ pci/include/linux/pci.h
> > @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> > unsigned long pci_address_to_pio(phys_addr_t addr);
> > phys_addr_t pci_pio_to_address(unsigned long pio);
> > int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr);
> > void pci_unmap_iospace(struct resource *res);
> > void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> > resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-28 14:26 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-06-28 14:26 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, Sergei Shtylyov,
linux-pci, Linus Walleij, linux-renesas-soc, Matthias Brugger,
Ryder Lee, linux-mediatek, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-arm-kernel
On Thu, Jun 28, 2018 at 08:22:59AM -0500, Bjorn Helgaas wrote:
> On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> > When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >
> > [ 1.225819] kernel BUG at lib/ioremap.c:72!
> > [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> > [ 1.235496] Modules linked in:
> > [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> > [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> > [ 1.252075] Workqueue: events deferred_probe_work_func
> > [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> > [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> > [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> > [ 1.271002] sp : ffff000008da39e0
> > [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> > [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> > [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> > [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> > [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> > [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> > [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> > [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> > [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> > [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> > [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> > [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> > [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> > [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> > [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> > [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> > [ 1.361056] Call trace:
> > [ 1.363504] ioremap_page_range+0x370/0x3c8
> > [ 1.367695] pci_remap_iospace+0x7c/0xac
> > [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> > [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> > [ 1.380786] platform_drv_probe+0x50/0xbc
> > [ 1.384799] driver_probe_device+0x21c/0x308
> > [ 1.389072] __device_attach_driver+0x98/0xc8
> > [ 1.393431] bus_for_each_drv+0x54/0x94
> > [ 1.397269] __device_attach+0xc4/0x12c
> > [ 1.401107] device_initial_probe+0x10/0x18
> > [ 1.405292] bus_probe_device+0x90/0x98
> > [ 1.409130] deferred_probe_work_func+0xb0/0x150
> > [ 1.413756] process_one_work+0x12c/0x29c
> > [ 1.417768] worker_thread+0x200/0x3fc
> > [ 1.421522] kthread+0x108/0x134
> > [ 1.424755] ret_from_fork+0x10/0x18
> > [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >
> > It turned out that pci_remap_iospace() wasn't undone when the driver's
> > probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > the probe was retried, finally causing the BUG due to trying to remap
> > already remapped pages.
> >
> > The most feasible solution seems to introduce devm_pci_remap_iospace()
> > and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > automagically on any probe failure.
> >
> > And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > drivers that have probably copied the bad example...
> >
> > Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > Cc: stable@vger.kernel.org
>
> Let me know if you want me to take this, Lorenzo, otherwise:
> s/pci: fix/PCI: Fix/ and
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
more so given the stable tag (and I think that each "Fixes" tag should
be self-contained), merging it as-is would give Greg (and us) a
headache when it comes to backporting it.
Honestly I think it is best to split it up and send it for v4.19 but
I am happy to hear other options.
Lorenzo
> > ---
> > The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> > It has only been tested with the R-Car PCIe driver...
> >
> > drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> > drivers/pci/controller/pci-aardvark.c | 2 -
> > drivers/pci/controller/pci-ftpci100.c | 2 -
> > drivers/pci/controller/pci-v3-semi.c | 2 -
> > drivers/pci/controller/pci-versatile.c | 2 -
> > drivers/pci/controller/pci-xgene.c | 2 -
> > drivers/pci/controller/pcie-mediatek.c | 2 -
> > drivers/pci/of.c | 2 -
> > drivers/pci/pci.c | 38 ++++++++++++++++++++++
> > include/linux/pci.h | 2 +
> > 10 files changed, 49 insertions(+), 8 deletions(-)
> >
> > Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> > +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> > resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> > switch (resource_type(win->res)) {
> > case IORESOURCE_IO:
> > - ret = pci_remap_iospace(win->res, pp->io_base);
> > + ret = devm_pci_remap_iospace(dev, win->res,
> > + pp->io_base);
> > if (ret) {
> > dev_warn(dev, "Error %d: failed to map resource %pR\n",
> > ret, win->res);
> > Index: pci/drivers/pci/controller/pci-aardvark.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-aardvark.c
> > +++ pci/drivers/pci/controller/pci-aardvark.c
> > @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> > 0, 0xF8000000, 0,
> > lower_32_bits(res->start),
> > OB_PCIE_IO);
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-ftpci100.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> > +++ pci/drivers/pci/controller/pci-ftpci100.c
> > @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> > dev_err(dev, "illegal IO mem size\n");
> > return -EINVAL;
> > }
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > ret, io);
> > Index: pci/drivers/pci/controller/pci-v3-semi.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> > +++ pci/drivers/pci/controller/pci-v3-semi.c
> > @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> > v3->io_bus_addr = io->start - win->offset;
> > dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> > io, &v3->io_bus_addr);
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev,
> > "error %d: failed to map resource %pR\n",
> > Index: pci/drivers/pci/controller/pci-versatile.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-versatile.c
> > +++ pci/drivers/pci/controller/pci-versatile.c
> > @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-xgene.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-xgene.c
> > +++ pci/drivers/pci/controller/pci-xgene.c
> > @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> > case IORESOURCE_IO:
> > xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> > res->start - window->offset);
> > - ret = pci_remap_iospace(res, io_base);
> > + ret = devm_pci_remap_iospace(dev, res, io_base);
> > if (ret < 0)
> > return ret;
> > break;
> > Index: pci/drivers/pci/controller/pcie-mediatek.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> > +++ pci/drivers/pci/controller/pcie-mediatek.c
> > @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> > if (err < 0)
> > return err;
> >
> > - pci_remap_iospace(&pcie->pio, pcie->io.start);
> > + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
> >
> > return 0;
> > }
> > Index: pci/drivers/pci/of.c
> > ===================================================================
> > --- pci.orig/drivers/pci/of.c
> > +++ pci/drivers/pci/of.c
> > @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/pci.c
> > ===================================================================
> > --- pci.orig/drivers/pci/pci.c
> > +++ pci/drivers/pci/pci.c
> > @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> > }
> > EXPORT_SYMBOL(pci_unmap_iospace);
> >
> > +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> > +{
> > + struct resource **res = ptr;
> > +
> > + pci_unmap_iospace(*res);
> > +}
> > +
> > +/**
> > + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> > + * @dev: Generic device to remap IO address for
> > + * @res: Resource describing the I/O space
> > + * @phys_addr: physical address of range to be mapped
> > + *
> > + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> > + * detach.
> > + */
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr)
> > +{
> > + const struct resource **ptr;
> > + int error;
> > +
> > + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> > + if (!ptr)
> > + return -ENOMEM;
> > +
> > + error = pci_remap_iospace(res, phys_addr);
> > + if (error) {
> > + devres_free(ptr);
> > + } else {
> > + *ptr = res;
> > + devres_add(dev, ptr);
> > + }
> > +
> > + return error;
> > +}
> > +EXPORT_SYMBOL(devm_pci_remap_iospace);
> > +
> > /**
> > * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> > * @dev: Generic device to remap IO address for
> > Index: pci/include/linux/pci.h
> > ===================================================================
> > --- pci.orig/include/linux/pci.h
> > +++ pci/include/linux/pci.h
> > @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> > unsigned long pci_address_to_pio(phys_addr_t addr);
> > phys_addr_t pci_pio_to_address(unsigned long pio);
> > int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr);
> > void pci_unmap_iospace(struct resource *res);
> > void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> > resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-28 14:26 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-06-28 14:26 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Jun 28, 2018 at 08:22:59AM -0500, Bjorn Helgaas wrote:
> On Wed, Jun 20, 2018 at 08:51:37PM +0300, Sergei Shtylyov wrote:
> > When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >
> > [ 1.225819] kernel BUG at lib/ioremap.c:72!
> > [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> > [ 1.235496] Modules linked in:
> > [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> > [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> > [ 1.252075] Workqueue: events deferred_probe_work_func
> > [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> > [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> > [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> > [ 1.271002] sp : ffff000008da39e0
> > [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> > [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> > [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> > [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> > [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> > [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> > [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> > [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> > [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> > [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> > [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> > [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> > [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> > [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> > [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> > [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> > [ 1.361056] Call trace:
> > [ 1.363504] ioremap_page_range+0x370/0x3c8
> > [ 1.367695] pci_remap_iospace+0x7c/0xac
> > [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> > [ 1.376945] rcar_pcie_probe+0x4c/0xb04
> > [ 1.380786] platform_drv_probe+0x50/0xbc
> > [ 1.384799] driver_probe_device+0x21c/0x308
> > [ 1.389072] __device_attach_driver+0x98/0xc8
> > [ 1.393431] bus_for_each_drv+0x54/0x94
> > [ 1.397269] __device_attach+0xc4/0x12c
> > [ 1.401107] device_initial_probe+0x10/0x18
> > [ 1.405292] bus_probe_device+0x90/0x98
> > [ 1.409130] deferred_probe_work_func+0xb0/0x150
> > [ 1.413756] process_one_work+0x12c/0x29c
> > [ 1.417768] worker_thread+0x200/0x3fc
> > [ 1.421522] kthread+0x108/0x134
> > [ 1.424755] ret_from_fork+0x10/0x18
> > [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >
> > It turned out that pci_remap_iospace() wasn't undone when the driver's
> > probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > the probe was retried, finally causing the BUG due to trying to remap
> > already remapped pages.
> >
> > The most feasible solution seems to introduce devm_pci_remap_iospace()
> > and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > automagically on any probe failure.
> >
> > And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > drivers that have probably copied the bad example...
> >
> > Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > Cc: stable at vger.kernel.org
>
> Let me know if you want me to take this, Lorenzo, otherwise:
> s/pci: fix/PCI: Fix/ and
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
more so given the stable tag (and I think that each "Fixes" tag should
be self-contained), merging it as-is would give Greg (and us) a
headache when it comes to backporting it.
Honestly I think it is best to split it up and send it for v4.19 but
I am happy to hear other options.
Lorenzo
> > ---
> > The patch is against the 'master' branch of Bjorn Helgaas' 'pci.git' repo...
> > It has only been tested with the R-Car PCIe driver...
> >
> > drivers/pci/controller/dwc/pcie-designware-host.c | 3 +
> > drivers/pci/controller/pci-aardvark.c | 2 -
> > drivers/pci/controller/pci-ftpci100.c | 2 -
> > drivers/pci/controller/pci-v3-semi.c | 2 -
> > drivers/pci/controller/pci-versatile.c | 2 -
> > drivers/pci/controller/pci-xgene.c | 2 -
> > drivers/pci/controller/pcie-mediatek.c | 2 -
> > drivers/pci/of.c | 2 -
> > drivers/pci/pci.c | 38 ++++++++++++++++++++++
> > include/linux/pci.h | 2 +
> > 10 files changed, 49 insertions(+), 8 deletions(-)
> >
> > Index: pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/dwc/pcie-designware-host.c
> > +++ pci/drivers/pci/controller/dwc/pcie-designware-host.c
> > @@ -363,7 +363,8 @@ int dw_pcie_host_init(struct pcie_port *
> > resource_list_for_each_entry_safe(win, tmp, &bridge->windows) {
> > switch (resource_type(win->res)) {
> > case IORESOURCE_IO:
> > - ret = pci_remap_iospace(win->res, pp->io_base);
> > + ret = devm_pci_remap_iospace(dev, win->res,
> > + pp->io_base);
> > if (ret) {
> > dev_warn(dev, "Error %d: failed to map resource %pR\n",
> > ret, win->res);
> > Index: pci/drivers/pci/controller/pci-aardvark.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-aardvark.c
> > +++ pci/drivers/pci/controller/pci-aardvark.c
> > @@ -849,7 +849,7 @@ static int advk_pcie_parse_request_of_pc
> > 0, 0xF8000000, 0,
> > lower_32_bits(res->start),
> > OB_PCIE_IO);
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-ftpci100.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-ftpci100.c
> > +++ pci/drivers/pci/controller/pci-ftpci100.c
> > @@ -501,7 +501,7 @@ static int faraday_pci_probe(struct plat
> > dev_err(dev, "illegal IO mem size\n");
> > return -EINVAL;
> > }
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > ret, io);
> > Index: pci/drivers/pci/controller/pci-v3-semi.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-v3-semi.c
> > +++ pci/drivers/pci/controller/pci-v3-semi.c
> > @@ -537,7 +537,7 @@ static int v3_pci_setup_resource(struct
> > v3->io_bus_addr = io->start - win->offset;
> > dev_dbg(dev, "I/O window %pR, bus addr %pap\n",
> > io, &v3->io_bus_addr);
> > - ret = pci_remap_iospace(io, io_base);
> > + ret = devm_pci_remap_iospace(dev, io, io_base);
> > if (ret) {
> > dev_warn(dev,
> > "error %d: failed to map resource %pR\n",
> > Index: pci/drivers/pci/controller/pci-versatile.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-versatile.c
> > +++ pci/drivers/pci/controller/pci-versatile.c
> > @@ -82,7 +82,7 @@ static int versatile_pci_parse_request_o
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/controller/pci-xgene.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pci-xgene.c
> > +++ pci/drivers/pci/controller/pci-xgene.c
> > @@ -423,7 +423,7 @@ static int xgene_pcie_map_ranges(struct
> > case IORESOURCE_IO:
> > xgene_pcie_setup_ob_reg(port, res, OMR3BARL, io_base,
> > res->start - window->offset);
> > - ret = pci_remap_iospace(res, io_base);
> > + ret = devm_pci_remap_iospace(dev, res, io_base);
> > if (ret < 0)
> > return ret;
> > break;
> > Index: pci/drivers/pci/controller/pcie-mediatek.c
> > ===================================================================
> > --- pci.orig/drivers/pci/controller/pcie-mediatek.c
> > +++ pci/drivers/pci/controller/pcie-mediatek.c
> > @@ -1109,7 +1109,7 @@ static int mtk_pcie_request_resources(st
> > if (err < 0)
> > return err;
> >
> > - pci_remap_iospace(&pcie->pio, pcie->io.start);
> > + devm_pci_remap_iospace(dev, &pcie->pio, pcie->io.start);
> >
> > return 0;
> > }
> > Index: pci/drivers/pci/of.c
> > ===================================================================
> > --- pci.orig/drivers/pci/of.c
> > +++ pci/drivers/pci/of.c
> > @@ -612,7 +612,7 @@ int pci_parse_request_of_pci_ranges(stru
> >
> > switch (resource_type(res)) {
> > case IORESOURCE_IO:
> > - err = pci_remap_iospace(res, iobase);
> > + err = devm_pci_remap_iospace(dev, res, iobase);
> > if (err) {
> > dev_warn(dev, "error %d: failed to map resource %pR\n",
> > err, res);
> > Index: pci/drivers/pci/pci.c
> > ===================================================================
> > --- pci.orig/drivers/pci/pci.c
> > +++ pci/drivers/pci/pci.c
> > @@ -3579,6 +3579,44 @@ void pci_unmap_iospace(struct resource *
> > }
> > EXPORT_SYMBOL(pci_unmap_iospace);
> >
> > +static void devm_pci_unmap_iospace(struct device *dev, void *ptr)
> > +{
> > + struct resource **res = ptr;
> > +
> > + pci_unmap_iospace(*res);
> > +}
> > +
> > +/**
> > + * devm_pci_remap_iospace - Managed pci_remap_iospace()
> > + * @dev: Generic device to remap IO address for
> > + * @res: Resource describing the I/O space
> > + * @phys_addr: physical address of range to be mapped
> > + *
> > + * Managed pci_remap_iospace(). Map is automatically unmapped on driver
> > + * detach.
> > + */
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr)
> > +{
> > + const struct resource **ptr;
> > + int error;
> > +
> > + ptr = devres_alloc(devm_pci_unmap_iospace, sizeof(*ptr), GFP_KERNEL);
> > + if (!ptr)
> > + return -ENOMEM;
> > +
> > + error = pci_remap_iospace(res, phys_addr);
> > + if (error) {
> > + devres_free(ptr);
> > + } else {
> > + *ptr = res;
> > + devres_add(dev, ptr);
> > + }
> > +
> > + return error;
> > +}
> > +EXPORT_SYMBOL(devm_pci_remap_iospace);
> > +
> > /**
> > * devm_pci_remap_cfgspace - Managed pci_remap_cfgspace()
> > * @dev: Generic device to remap IO address for
> > Index: pci/include/linux/pci.h
> > ===================================================================
> > --- pci.orig/include/linux/pci.h
> > +++ pci/include/linux/pci.h
> > @@ -1240,6 +1240,8 @@ int pci_register_io_range(struct fwnode_
> > unsigned long pci_address_to_pio(phys_addr_t addr);
> > phys_addr_t pci_pio_to_address(unsigned long pio);
> > int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr);
> > +int devm_pci_remap_iospace(struct device *dev, const struct resource *res,
> > + phys_addr_t phys_addr);
> > void pci_unmap_iospace(struct resource *res);
> > void __iomem *devm_pci_remap_cfgspace(struct device *dev,
> > resource_size_t offset,
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-28 14:26 ` Lorenzo Pieralisi
(?)
@ 2018-06-30 10:37 ` Sergei Shtylyov
-1 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-30 10:37 UTC (permalink / raw)
To: Lorenzo Pieralisi, Bjorn Helgaas
Cc: Bjorn Helgaas, linux-pci, Linus Walleij, Jingoo Han, Joao Pinto,
Thomas Petazzoni, Rob Herring, Tanmay Inamdar, Ryder Lee,
Matthias Brugger, linux-arm-kernel, linux-mediatek,
linux-renesas-soc
Hello!
On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>
>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>> [ 1.235496] Modules linked in:
>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>> [ 1.271002] sp : ffff000008da39e0
>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>> [ 1.361056] Call trace:
>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>> [ 1.397269] __device_attach+0xc4/0x12c
>>> [ 1.401107] device_initial_probe+0x10/0x18
>>> [ 1.405292] bus_probe_device+0x90/0x98
>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>> [ 1.413756] process_one_work+0x12c/0x29c
>>> [ 1.417768] worker_thread+0x200/0x3fc
>>> [ 1.421522] kthread+0x108/0x134
>>> [ 1.424755] ret_from_fork+0x10/0x18
>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>
>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>> the probe was retried, finally causing the BUG due to trying to remap
>>> already remapped pages.
>>>
>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>> automagically on any probe failure.
>>>
>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>> drivers that have probably copied the bad example...
>>>
>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Cc: stable@vger.kernel.org
>>
>> Let me know if you want me to take this, Lorenzo, otherwise:
>> s/pci: fix/PCI: Fix/ and
>>
>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> more so given the stable tag (and I think that each "Fixes" tag should
> be self-contained),
It cannot be self-contained because it'll depend on the initial commit
adding devm_pci_remap_iobase(). If you mean finding the earliest broken driver
and introduce the deviec managed API while fixing it and then make use of that
API in the subsequent patches, that surely can be done.
> merging it as-is would give Greg (and us) a
> headache when it comes to backporting it.
The patch interdependency would give him headache too, and I was hoping to
relieve those with the monilitic patch. :-)
> Honestly I think it is best to split it up and send it for v4.19 but
> I am happy to hear other options.
I disagree about 4.19. The R-Car PCIe situation is as follows: given me
missing to get the PHY driver merged into 4.18 (and the gen3 PCIe stuff
successfully merged into 4.18), the user is bound to have PCIe not working (if
he doesn't refer to the PHY driver in DT) or encounter a kernel BUG (if he
does refer to the PHY driver), thus I'd like this BUG to be fixed in 4.18 time
frame...
Note that any PCI driver having signaled a probe deferral will also hit
this BUG., not just R-Car one.
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-06-30 10:37 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-30 10:37 UTC (permalink / raw)
To: Lorenzo Pieralisi, Bjorn Helgaas
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, linux-renesas-soc, Matthias Brugger, Ryder Lee,
linux-mediatek, Tanmay Inamdar, Jingoo Han, Bjorn Helgaas,
linux-arm-kernel
Hello!
On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>
>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>> [ 1.235496] Modules linked in:
>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>> [ 1.271002] sp : ffff000008da39e0
>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>> [ 1.361056] Call trace:
>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>> [ 1.397269] __device_attach+0xc4/0x12c
>>> [ 1.401107] device_initial_probe+0x10/0x18
>>> [ 1.405292] bus_probe_device+0x90/0x98
>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>> [ 1.413756] process_one_work+0x12c/0x29c
>>> [ 1.417768] worker_thread+0x200/0x3fc
>>> [ 1.421522] kthread+0x108/0x134
>>> [ 1.424755] ret_from_fork+0x10/0x18
>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>
>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>> the probe was retried, finally causing the BUG due to trying to remap
>>> already remapped pages.
>>>
>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>> automagically on any probe failure.
>>>
>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>> drivers that have probably copied the bad example...
>>>
>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Cc: stable@vger.kernel.org
>>
>> Let me know if you want me to take this, Lorenzo, otherwise:
>> s/pci: fix/PCI: Fix/ and
>>
>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> more so given the stable tag (and I think that each "Fixes" tag should
> be self-contained),
It cannot be self-contained because it'll depend on the initial commit
adding devm_pci_remap_iobase(). If you mean finding the earliest broken driver
and introduce the deviec managed API while fixing it and then make use of that
API in the subsequent patches, that surely can be done.
> merging it as-is would give Greg (and us) a
> headache when it comes to backporting it.
The patch interdependency would give him headache too, and I was hoping to
relieve those with the monilitic patch. :-)
> Honestly I think it is best to split it up and send it for v4.19 but
> I am happy to hear other options.
I disagree about 4.19. The R-Car PCIe situation is as follows: given me
missing to get the PHY driver merged into 4.18 (and the gen3 PCIe stuff
successfully merged into 4.18), the user is bound to have PCIe not working (if
he doesn't refer to the PHY driver in DT) or encounter a kernel BUG (if he
does refer to the PHY driver), thus I'd like this BUG to be fixed in 4.18 time
frame...
Note that any PCI driver having signaled a probe deferral will also hit
this BUG., not just R-Car one.
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-06-30 10:37 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-06-30 10:37 UTC (permalink / raw)
To: linux-arm-kernel
Hello!
On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>
>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>> [ 1.235496] Modules linked in:
>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>> [ 1.271002] sp : ffff000008da39e0
>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>> [ 1.361056] Call trace:
>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>> [ 1.397269] __device_attach+0xc4/0x12c
>>> [ 1.401107] device_initial_probe+0x10/0x18
>>> [ 1.405292] bus_probe_device+0x90/0x98
>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>> [ 1.413756] process_one_work+0x12c/0x29c
>>> [ 1.417768] worker_thread+0x200/0x3fc
>>> [ 1.421522] kthread+0x108/0x134
>>> [ 1.424755] ret_from_fork+0x10/0x18
>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>
>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>> the probe was retried, finally causing the BUG due to trying to remap
>>> already remapped pages.
>>>
>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>> automagically on any probe failure.
>>>
>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>> drivers that have probably copied the bad example...
>>>
>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Cc: stable at vger.kernel.org
>>
>> Let me know if you want me to take this, Lorenzo, otherwise:
>> s/pci: fix/PCI: Fix/ and
>>
>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> more so given the stable tag (and I think that each "Fixes" tag should
> be self-contained),
It cannot be self-contained because it'll depend on the initial commit
adding devm_pci_remap_iobase(). If you mean finding the earliest broken driver
and introduce the deviec managed API while fixing it and then make use of that
API in the subsequent patches, that surely can be done.
> merging it as-is would give Greg (and us) a
> headache when it comes to backporting it.
The patch interdependency would give him headache too, and I was hoping to
relieve those with the monilitic patch. :-)
> Honestly I think it is best to split it up and send it for v4.19 but
> I am happy to hear other options.
I disagree about 4.19. The R-Car PCIe situation is as follows: given me
missing to get the PHY driver merged into 4.18 (and the gen3 PCIe stuff
successfully merged into 4.18), the user is bound to have PCIe not working (if
he doesn't refer to the PHY driver in DT) or encounter a kernel BUG (if he
does refer to the PHY driver), thus I'd like this BUG to be fixed in 4.18 time
frame...
Note that any PCI driver having signaled a probe deferral will also hit
this BUG., not just R-Car one.
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-06-30 10:37 ` Sergei Shtylyov
(?)
@ 2018-07-02 10:33 ` Lorenzo Pieralisi
-1 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 10:33 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Bjorn Helgaas, Bjorn Helgaas, linux-pci, Linus Walleij,
Jingoo Han, Joao Pinto, Thomas Petazzoni, Rob Herring,
Tanmay Inamdar, Ryder Lee, Matthias Brugger, linux-arm-kernel,
linux-mediatek, linux-renesas-soc
On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>
> >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >>>
> >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> >>>[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> >>>[ 1.235496] Modules linked in:
> >>>[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> >>>[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> >>>[ 1.252075] Workqueue: events deferred_probe_work_func
> >>>[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> >>>[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> >>>[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> >>>[ 1.271002] sp : ffff000008da39e0
> >>>[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> >>>[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> >>>[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> >>>[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> >>>[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> >>>[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> >>>[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> >>>[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> >>>[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> >>>[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> >>>[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> >>>[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> >>>[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> >>>[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> >>>[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> >>>[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> >>>[ 1.361056] Call trace:
> >>>[ 1.363504] ioremap_page_range+0x370/0x3c8
> >>>[ 1.367695] pci_remap_iospace+0x7c/0xac
> >>>[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> >>>[ 1.376945] rcar_pcie_probe+0x4c/0xb04
> >>>[ 1.380786] platform_drv_probe+0x50/0xbc
> >>>[ 1.384799] driver_probe_device+0x21c/0x308
> >>>[ 1.389072] __device_attach_driver+0x98/0xc8
> >>>[ 1.393431] bus_for_each_drv+0x54/0x94
> >>>[ 1.397269] __device_attach+0xc4/0x12c
> >>>[ 1.401107] device_initial_probe+0x10/0x18
> >>>[ 1.405292] bus_probe_device+0x90/0x98
> >>>[ 1.409130] deferred_probe_work_func+0xb0/0x150
> >>>[ 1.413756] process_one_work+0x12c/0x29c
> >>>[ 1.417768] worker_thread+0x200/0x3fc
> >>>[ 1.421522] kthread+0x108/0x134
> >>>[ 1.424755] ret_from_fork+0x10/0x18
> >>>[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >>>
> >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> >>>the probe was retried, finally causing the BUG due to trying to remap
> >>>already remapped pages.
> >>>
> >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> >>>automagically on any probe failure.
> >>>
> >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> >>>drivers that have probably copied the bad example...
> >>>
> >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >>>Cc: stable@vger.kernel.org
> >>
> >>Let me know if you want me to take this, Lorenzo, otherwise:
> >>s/pci: fix/PCI: Fix/ and
> >>
> >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> >
> >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> >more so given the stable tag (and I think that each "Fixes" tag should
> >be self-contained),
>
> It cannot be self-contained because it'll depend on the initial
> commit adding devm_pci_remap_iobase(). If you mean finding the
> earliest broken driver and introduce the deviec managed API while
> fixing it and then make use of that
> API in the subsequent patches, that surely can be done.
Yes I think that's the best course of action.
> >merging it as-is would give Greg (and us) a
> >headache when it comes to backporting it.
>
> The patch interdependency would give him headache too, and I was
> hoping to relieve those with the monilitic patch. :-)
The problem is that if any of the fixes has to be reverted we have
to revert the whole thing instead of just the problematic patch,
which, given that we are sending this to stable kernels may easily
turn out quite complicated.
So, I would add the new API along with the earliest broken driver
and mark it for stable.
In the same thread, add all other fixes (one per patch) without the
stable tag. When the first fix gets merged into the mainline (and
consequently goes to stable) we can send the stable backports for the
remainder of fixes.
How does that sound ?
> >Honestly I think it is best to split it up and send it for v4.19 but
> >I am happy to hear other options.
>
> I disagree about 4.19. The R-Car PCIe situation is as follows:
> given me missing to get the PHY driver merged into 4.18 (and the
> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
> have PCIe not working (if he doesn't refer to the PHY driver in DT)
> or encounter a kernel BUG (if he does refer to the PHY driver), thus
> I'd like this BUG to be fixed in 4.18 time frame...
We shall try, please let me know if you are able to respin asap,
we already have a bunch of fixes queued.
Thanks for putting it together,
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-07-02 10:33 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 10:33 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, linux-renesas-soc, Matthias Brugger, Ryder Lee,
Bjorn Helgaas, Tanmay Inamdar, Jingoo Han, Bjorn Helgaas,
linux-mediatek, linux-arm-kernel
On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>
> >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >>>
> >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> >>>[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> >>>[ 1.235496] Modules linked in:
> >>>[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> >>>[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> >>>[ 1.252075] Workqueue: events deferred_probe_work_func
> >>>[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> >>>[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> >>>[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> >>>[ 1.271002] sp : ffff000008da39e0
> >>>[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> >>>[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> >>>[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> >>>[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> >>>[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> >>>[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> >>>[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> >>>[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> >>>[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> >>>[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> >>>[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> >>>[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> >>>[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> >>>[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> >>>[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> >>>[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> >>>[ 1.361056] Call trace:
> >>>[ 1.363504] ioremap_page_range+0x370/0x3c8
> >>>[ 1.367695] pci_remap_iospace+0x7c/0xac
> >>>[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> >>>[ 1.376945] rcar_pcie_probe+0x4c/0xb04
> >>>[ 1.380786] platform_drv_probe+0x50/0xbc
> >>>[ 1.384799] driver_probe_device+0x21c/0x308
> >>>[ 1.389072] __device_attach_driver+0x98/0xc8
> >>>[ 1.393431] bus_for_each_drv+0x54/0x94
> >>>[ 1.397269] __device_attach+0xc4/0x12c
> >>>[ 1.401107] device_initial_probe+0x10/0x18
> >>>[ 1.405292] bus_probe_device+0x90/0x98
> >>>[ 1.409130] deferred_probe_work_func+0xb0/0x150
> >>>[ 1.413756] process_one_work+0x12c/0x29c
> >>>[ 1.417768] worker_thread+0x200/0x3fc
> >>>[ 1.421522] kthread+0x108/0x134
> >>>[ 1.424755] ret_from_fork+0x10/0x18
> >>>[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >>>
> >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> >>>the probe was retried, finally causing the BUG due to trying to remap
> >>>already remapped pages.
> >>>
> >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> >>>automagically on any probe failure.
> >>>
> >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> >>>drivers that have probably copied the bad example...
> >>>
> >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >>>Cc: stable@vger.kernel.org
> >>
> >>Let me know if you want me to take this, Lorenzo, otherwise:
> >>s/pci: fix/PCI: Fix/ and
> >>
> >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> >
> >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> >more so given the stable tag (and I think that each "Fixes" tag should
> >be self-contained),
>
> It cannot be self-contained because it'll depend on the initial
> commit adding devm_pci_remap_iobase(). If you mean finding the
> earliest broken driver and introduce the deviec managed API while
> fixing it and then make use of that
> API in the subsequent patches, that surely can be done.
Yes I think that's the best course of action.
> >merging it as-is would give Greg (and us) a
> >headache when it comes to backporting it.
>
> The patch interdependency would give him headache too, and I was
> hoping to relieve those with the monilitic patch. :-)
The problem is that if any of the fixes has to be reverted we have
to revert the whole thing instead of just the problematic patch,
which, given that we are sending this to stable kernels may easily
turn out quite complicated.
So, I would add the new API along with the earliest broken driver
and mark it for stable.
In the same thread, add all other fixes (one per patch) without the
stable tag. When the first fix gets merged into the mainline (and
consequently goes to stable) we can send the stable backports for the
remainder of fixes.
How does that sound ?
> >Honestly I think it is best to split it up and send it for v4.19 but
> >I am happy to hear other options.
>
> I disagree about 4.19. The R-Car PCIe situation is as follows:
> given me missing to get the PHY driver merged into 4.18 (and the
> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
> have PCIe not working (if he doesn't refer to the PHY driver in DT)
> or encounter a kernel BUG (if he does refer to the PHY driver), thus
> I'd like this BUG to be fixed in 4.18 time frame...
We shall try, please let me know if you are able to respin asap,
we already have a bunch of fixes queued.
Thanks for putting it together,
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-07-02 10:33 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 10:33 UTC (permalink / raw)
To: linux-arm-kernel
On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
>
> >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> >>>
> >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> >>>[ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> >>>[ 1.235496] Modules linked in:
> >>>[ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
> >>>[ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
> >>>[ 1.252075] Workqueue: events deferred_probe_work_func
> >>>[ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
> >>>[ 1.262024] pc : ioremap_page_range+0x370/0x3c8
> >>>[ 1.266558] lr : ioremap_page_range+0x40/0x3c8
> >>>[ 1.271002] sp : ffff000008da39e0
> >>>[ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
> >>>[ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
> >>>[ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
> >>>[ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
> >>>[ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
> >>>[ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
> >>>[ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
> >>>[ 1.311544] x15: 0000000000000000 x14: 0720072007200720
> >>>[ 1.316862] x13: 0720072007200720 x12: 0720072007200720
> >>>[ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
> >>>[ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
> >>>[ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
> >>>[ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
> >>>[ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
> >>>[ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
> >>>[ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
> >>>[ 1.361056] Call trace:
> >>>[ 1.363504] ioremap_page_range+0x370/0x3c8
> >>>[ 1.367695] pci_remap_iospace+0x7c/0xac
> >>>[ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
> >>>[ 1.376945] rcar_pcie_probe+0x4c/0xb04
> >>>[ 1.380786] platform_drv_probe+0x50/0xbc
> >>>[ 1.384799] driver_probe_device+0x21c/0x308
> >>>[ 1.389072] __device_attach_driver+0x98/0xc8
> >>>[ 1.393431] bus_for_each_drv+0x54/0x94
> >>>[ 1.397269] __device_attach+0xc4/0x12c
> >>>[ 1.401107] device_initial_probe+0x10/0x18
> >>>[ 1.405292] bus_probe_device+0x90/0x98
> >>>[ 1.409130] deferred_probe_work_func+0xb0/0x150
> >>>[ 1.413756] process_one_work+0x12c/0x29c
> >>>[ 1.417768] worker_thread+0x200/0x3fc
> >>>[ 1.421522] kthread+0x108/0x134
> >>>[ 1.424755] ret_from_fork+0x10/0x18
> >>>[ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
> >>>
> >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> >>>the probe was retried, finally causing the BUG due to trying to remap
> >>>already remapped pages.
> >>>
> >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> >>>automagically on any probe failure.
> >>>
> >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> >>>drivers that have probably copied the bad example...
> >>>
> >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >>>Cc: stable at vger.kernel.org
> >>
> >>Let me know if you want me to take this, Lorenzo, otherwise:
> >>s/pci: fix/PCI: Fix/ and
> >>
> >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> >
> >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> >more so given the stable tag (and I think that each "Fixes" tag should
> >be self-contained),
>
> It cannot be self-contained because it'll depend on the initial
> commit adding devm_pci_remap_iobase(). If you mean finding the
> earliest broken driver and introduce the deviec managed API while
> fixing it and then make use of that
> API in the subsequent patches, that surely can be done.
Yes I think that's the best course of action.
> >merging it as-is would give Greg (and us) a
> >headache when it comes to backporting it.
>
> The patch interdependency would give him headache too, and I was
> hoping to relieve those with the monilitic patch. :-)
The problem is that if any of the fixes has to be reverted we have
to revert the whole thing instead of just the problematic patch,
which, given that we are sending this to stable kernels may easily
turn out quite complicated.
So, I would add the new API along with the earliest broken driver
and mark it for stable.
In the same thread, add all other fixes (one per patch) without the
stable tag. When the first fix gets merged into the mainline (and
consequently goes to stable) we can send the stable backports for the
remainder of fixes.
How does that sound ?
> >Honestly I think it is best to split it up and send it for v4.19 but
> >I am happy to hear other options.
>
> I disagree about 4.19. The R-Car PCIe situation is as follows:
> given me missing to get the PHY driver merged into 4.18 (and the
> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
> have PCIe not working (if he doesn't refer to the PHY driver in DT)
> or encounter a kernel BUG (if he does refer to the PHY driver), thus
> I'd like this BUG to be fixed in 4.18 time frame...
We shall try, please let me know if you are able to respin asap,
we already have a bunch of fixes queued.
Thanks for putting it together,
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-07-02 10:33 ` Lorenzo Pieralisi
(?)
@ 2018-07-02 11:08 ` Geert Uytterhoeven
-1 siblings, 0 replies; 37+ messages in thread
From: Geert Uytterhoeven @ 2018-07-02 11:08 UTC (permalink / raw)
To: Lorenzo Pieralisi
Cc: Sergei Shtylyov, Bjorn Helgaas, Bjorn Helgaas, linux-pci,
Linus Walleij, Jingoo Han, Joao.Pinto, Thomas Petazzoni,
Rob Herring, Tanmay Inamdar, ryder.lee, Matthias Brugger,
Linux ARM, linux-mediatek, Linux-Renesas
Hi Lorenzo,
On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
<lorenzo.pieralisi@arm.com> wrote:
> On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > >>>
> > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > >>>the probe was retried, finally causing the BUG due to trying to remap
> > >>>already remapped pages.
> > >>>
> > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > >>>automagically on any probe failure.
> > >>>
> > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > >>>drivers that have probably copied the bad example...
> > >>>
> > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > >>>Cc: stable@vger.kernel.org
> > >>
> > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > >>s/pci: fix/PCI: Fix/ and
> > >>
> > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > >
> > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > >more so given the stable tag (and I think that each "Fixes" tag should
> > >be self-contained),
> >
> > It cannot be self-contained because it'll depend on the initial
> > commit adding devm_pci_remap_iobase(). If you mean finding the
> > earliest broken driver and introduce the deviec managed API while
> > fixing it and then make use of that
> > API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
>
> > >merging it as-is would give Greg (and us) a
> > >headache when it comes to backporting it.
> >
> > The patch interdependency would give him headache too, and I was
> > hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
If you want to be prepared for reverting, why not split off the first fix
from the patch that provides the new API as well?
Yes, it does mean a dependency for backporting, but it avoids the mess if
it turns out the first fix is the (only) one that needs to be reverted.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-07-02 11:08 ` Geert Uytterhoeven
0 siblings, 0 replies; 37+ messages in thread
From: Geert Uytterhoeven @ 2018-07-02 11:08 UTC (permalink / raw)
To: Lorenzo Pieralisi
Cc: Thomas Petazzoni, Rob Herring, Joao.Pinto, Sergei Shtylyov,
linux-pci, Linus Walleij, Linux-Renesas, Matthias Brugger,
ryder.lee, Bjorn Helgaas, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-mediatek, Linux ARM
Hi Lorenzo,
On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
<lorenzo.pieralisi@arm.com> wrote:
> On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > >>>
> > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > >>>the probe was retried, finally causing the BUG due to trying to remap
> > >>>already remapped pages.
> > >>>
> > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > >>>automagically on any probe failure.
> > >>>
> > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > >>>drivers that have probably copied the bad example...
> > >>>
> > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > >>>Cc: stable@vger.kernel.org
> > >>
> > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > >>s/pci: fix/PCI: Fix/ and
> > >>
> > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > >
> > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > >more so given the stable tag (and I think that each "Fixes" tag should
> > >be self-contained),
> >
> > It cannot be self-contained because it'll depend on the initial
> > commit adding devm_pci_remap_iobase(). If you mean finding the
> > earliest broken driver and introduce the deviec managed API while
> > fixing it and then make use of that
> > API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
>
> > >merging it as-is would give Greg (and us) a
> > >headache when it comes to backporting it.
> >
> > The patch interdependency would give him headache too, and I was
> > hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
If you want to be prepared for reverting, why not split off the first fix
from the patch that provides the new API as well?
Yes, it does mean a dependency for backporting, but it avoids the mess if
it turns out the first fix is the (only) one that needs to be reverted.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-07-02 11:08 ` Geert Uytterhoeven
0 siblings, 0 replies; 37+ messages in thread
From: Geert Uytterhoeven @ 2018-07-02 11:08 UTC (permalink / raw)
To: linux-arm-kernel
Hi Lorenzo,
On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
<lorenzo.pieralisi@arm.com> wrote:
> On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > >>>
> > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
> > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > >>>the probe was retried, finally causing the BUG due to trying to remap
> > >>>already remapped pages.
> > >>>
> > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > >>>automagically on any probe failure.
> > >>>
> > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > >>>drivers that have probably copied the bad example...
> > >>>
> > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > >>>Cc: stable at vger.kernel.org
> > >>
> > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > >>s/pci: fix/PCI: Fix/ and
> > >>
> > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > >
> > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > >more so given the stable tag (and I think that each "Fixes" tag should
> > >be self-contained),
> >
> > It cannot be self-contained because it'll depend on the initial
> > commit adding devm_pci_remap_iobase(). If you mean finding the
> > earliest broken driver and introduce the deviec managed API while
> > fixing it and then make use of that
> > API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
>
> > >merging it as-is would give Greg (and us) a
> > >headache when it comes to backporting it.
> >
> > The patch interdependency would give him headache too, and I was
> > hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
If you want to be prepared for reverting, why not split off the first fix
from the patch that provides the new API as well?
Yes, it does mean a dependency for backporting, but it avoids the mess if
it turns out the first fix is the (only) one that needs to be reverted.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-07-02 11:08 ` Geert Uytterhoeven
(?)
@ 2018-07-02 14:12 ` Lorenzo Pieralisi
-1 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 14:12 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: Sergei Shtylyov, Bjorn Helgaas, Bjorn Helgaas, linux-pci,
Linus Walleij, Jingoo Han, Joao.Pinto, Thomas Petazzoni,
Rob Herring, Tanmay Inamdar, ryder.lee, Matthias Brugger,
Linux ARM, linux-mediatek, Linux-Renesas
On Mon, Jul 02, 2018 at 01:08:45PM +0200, Geert Uytterhoeven wrote:
> Hi Lorenzo,
>
> On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > > >>>
> > > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
>
> > > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > > >>>the probe was retried, finally causing the BUG due to trying to remap
> > > >>>already remapped pages.
> > > >>>
> > > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > > >>>automagically on any probe failure.
> > > >>>
> > > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > > >>>drivers that have probably copied the bad example...
> > > >>>
> > > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > > >>>Cc: stable@vger.kernel.org
> > > >>
> > > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > > >>s/pci: fix/PCI: Fix/ and
> > > >>
> > > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > > >
> > > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > > >more so given the stable tag (and I think that each "Fixes" tag should
> > > >be self-contained),
> > >
> > > It cannot be self-contained because it'll depend on the initial
> > > commit adding devm_pci_remap_iobase(). If you mean finding the
> > > earliest broken driver and introduce the deviec managed API while
> > > fixing it and then make use of that
> > > API in the subsequent patches, that surely can be done.
> >
> > Yes I think that's the best course of action.
> >
> > > >merging it as-is would give Greg (and us) a
> > > >headache when it comes to backporting it.
> > >
> > > The patch interdependency would give him headache too, and I was
> > > hoping to relieve those with the monilitic patch. :-)
> >
> > The problem is that if any of the fixes has to be reverted we have
> > to revert the whole thing instead of just the problematic patch,
> > which, given that we are sending this to stable kernels may easily
> > turn out quite complicated.
> >
> > So, I would add the new API along with the earliest broken driver
> > and mark it for stable.
> >
> > In the same thread, add all other fixes (one per patch) without the
> > stable tag. When the first fix gets merged into the mainline (and
> > consequently goes to stable) we can send the stable backports for the
> > remainder of fixes.
> >
> > How does that sound ?
>
> If you want to be prepared for reverting, why not split off the first fix
> from the patch that provides the new API as well?
> Yes, it does mean a dependency for backporting, but it avoids the mess if
> it turns out the first fix is the (only) one that needs to be reverted.
Problem is that that would give Bjorn a hard time asking to merge the
new API as a fix as a standalone patch for an -rc, hence I suggested we
merged it for v4.19 but Sergei is not happy with that and I understand
his point.
To be honest I'd rather start with fixing RCAR (by "fixing" the
pci_parse_request_of_pci_ranges() call with the new devm_ API) without
any stable tag (with commit log reporting the RCAR regression), we will
work out how to fix and backport the rest of the drivers later.
I am not even sure this fix per-se is stable kernel material, that's
moot given that there exists an pci_unmap_iospace() API that could be
used in drivers before they were converted to
pci_parse_request_of_pci_ranges().
Please let me know if that's reasonable, thanks.
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-07-02 14:12 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 14:12 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: Thomas Petazzoni, Rob Herring, Joao.Pinto, Sergei Shtylyov,
linux-pci, Linus Walleij, Linux-Renesas, Matthias Brugger,
ryder.lee, Bjorn Helgaas, Tanmay Inamdar, Jingoo Han,
Bjorn Helgaas, linux-mediatek, Linux ARM
On Mon, Jul 02, 2018 at 01:08:45PM +0200, Geert Uytterhoeven wrote:
> Hi Lorenzo,
>
> On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > > >>>
> > > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
>
> > > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > > >>>the probe was retried, finally causing the BUG due to trying to remap
> > > >>>already remapped pages.
> > > >>>
> > > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > > >>>automagically on any probe failure.
> > > >>>
> > > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > > >>>drivers that have probably copied the bad example...
> > > >>>
> > > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > > >>>Cc: stable@vger.kernel.org
> > > >>
> > > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > > >>s/pci: fix/PCI: Fix/ and
> > > >>
> > > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > > >
> > > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > > >more so given the stable tag (and I think that each "Fixes" tag should
> > > >be self-contained),
> > >
> > > It cannot be self-contained because it'll depend on the initial
> > > commit adding devm_pci_remap_iobase(). If you mean finding the
> > > earliest broken driver and introduce the deviec managed API while
> > > fixing it and then make use of that
> > > API in the subsequent patches, that surely can be done.
> >
> > Yes I think that's the best course of action.
> >
> > > >merging it as-is would give Greg (and us) a
> > > >headache when it comes to backporting it.
> > >
> > > The patch interdependency would give him headache too, and I was
> > > hoping to relieve those with the monilitic patch. :-)
> >
> > The problem is that if any of the fixes has to be reverted we have
> > to revert the whole thing instead of just the problematic patch,
> > which, given that we are sending this to stable kernels may easily
> > turn out quite complicated.
> >
> > So, I would add the new API along with the earliest broken driver
> > and mark it for stable.
> >
> > In the same thread, add all other fixes (one per patch) without the
> > stable tag. When the first fix gets merged into the mainline (and
> > consequently goes to stable) we can send the stable backports for the
> > remainder of fixes.
> >
> > How does that sound ?
>
> If you want to be prepared for reverting, why not split off the first fix
> from the patch that provides the new API as well?
> Yes, it does mean a dependency for backporting, but it avoids the mess if
> it turns out the first fix is the (only) one that needs to be reverted.
Problem is that that would give Bjorn a hard time asking to merge the
new API as a fix as a standalone patch for an -rc, hence I suggested we
merged it for v4.19 but Sergei is not happy with that and I understand
his point.
To be honest I'd rather start with fixing RCAR (by "fixing" the
pci_parse_request_of_pci_ranges() call with the new devm_ API) without
any stable tag (with commit log reporting the RCAR regression), we will
work out how to fix and backport the rest of the drivers later.
I am not even sure this fix per-se is stable kernel material, that's
moot given that there exists an pci_unmap_iospace() API that could be
used in drivers before they were converted to
pci_parse_request_of_pci_ranges().
Please let me know if that's reasonable, thanks.
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-07-02 14:12 ` Lorenzo Pieralisi
0 siblings, 0 replies; 37+ messages in thread
From: Lorenzo Pieralisi @ 2018-07-02 14:12 UTC (permalink / raw)
To: linux-arm-kernel
On Mon, Jul 02, 2018 at 01:08:45PM +0200, Geert Uytterhoeven wrote:
> Hi Lorenzo,
>
> On Mon, Jul 2, 2018 at 12:31 PM Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > On Sat, Jun 30, 2018 at 01:37:18PM +0300, Sergei Shtylyov wrote:
> > > On 6/28/2018 5:26 PM, Lorenzo Pieralisi wrote:
> > > >>>When testing the R-Car PCIe driver on the Condor board, I noticed that iff
> > > >>>I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
> > > >>>
> > > >>>[ 1.225819] kernel BUG at lib/ioremap.c:72!
>
> > > >>>It turned out that pci_remap_iospace() wasn't undone when the driver's
> > > >>>probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
> > > >>>the probe was retried, finally causing the BUG due to trying to remap
> > > >>>already remapped pages.
> > > >>>
> > > >>>The most feasible solution seems to introduce devm_pci_remap_iospace()
> > > >>>and call it instead of pci_remap_iospace(), so that the pages get unmapped
> > > >>>automagically on any probe failure.
> > > >>>
> > > >>>And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
> > > >>>drivers that have probably copied the bad example...
> > > >>>
> > > >>>Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
> > > >>>Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
> > > >>>Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
> > > >>>Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
> > > >>>Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
> > > >>>Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
> > > >>>Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
> > > >>>Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
> > > >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > > >>>Cc: stable at vger.kernel.org
> > > >>
> > > >>Let me know if you want me to take this, Lorenzo, otherwise:
> > > >>s/pci: fix/PCI: Fix/ and
> > > >>
> > > >>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > > >
> > > >Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
> > > >more so given the stable tag (and I think that each "Fixes" tag should
> > > >be self-contained),
> > >
> > > It cannot be self-contained because it'll depend on the initial
> > > commit adding devm_pci_remap_iobase(). If you mean finding the
> > > earliest broken driver and introduce the deviec managed API while
> > > fixing it and then make use of that
> > > API in the subsequent patches, that surely can be done.
> >
> > Yes I think that's the best course of action.
> >
> > > >merging it as-is would give Greg (and us) a
> > > >headache when it comes to backporting it.
> > >
> > > The patch interdependency would give him headache too, and I was
> > > hoping to relieve those with the monilitic patch. :-)
> >
> > The problem is that if any of the fixes has to be reverted we have
> > to revert the whole thing instead of just the problematic patch,
> > which, given that we are sending this to stable kernels may easily
> > turn out quite complicated.
> >
> > So, I would add the new API along with the earliest broken driver
> > and mark it for stable.
> >
> > In the same thread, add all other fixes (one per patch) without the
> > stable tag. When the first fix gets merged into the mainline (and
> > consequently goes to stable) we can send the stable backports for the
> > remainder of fixes.
> >
> > How does that sound ?
>
> If you want to be prepared for reverting, why not split off the first fix
> from the patch that provides the new API as well?
> Yes, it does mean a dependency for backporting, but it avoids the mess if
> it turns out the first fix is the (only) one that needs to be reverted.
Problem is that that would give Bjorn a hard time asking to merge the
new API as a fix as a standalone patch for an -rc, hence I suggested we
merged it for v4.19 but Sergei is not happy with that and I understand
his point.
To be honest I'd rather start with fixing RCAR (by "fixing" the
pci_parse_request_of_pci_ranges() call with the new devm_ API) without
any stable tag (with commit log reporting the RCAR regression), we will
work out how to fix and backport the rest of the drivers later.
I am not even sure this fix per-se is stable kernel material, that's
moot given that there exists an pci_unmap_iospace() API that could be
used in drivers before they were converted to
pci_parse_request_of_pci_ranges().
Please let me know if that's reasonable, thanks.
Lorenzo
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
2018-07-02 10:33 ` Lorenzo Pieralisi
(?)
@ 2018-07-02 19:40 ` Sergei Shtylyov
-1 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-07-02 19:40 UTC (permalink / raw)
To: Lorenzo Pieralisi
Cc: Bjorn Helgaas, Bjorn Helgaas, linux-pci, Linus Walleij,
Jingoo Han, Joao Pinto, Thomas Petazzoni, Rob Herring,
Tanmay Inamdar, Ryder Lee, Matthias Brugger, linux-arm-kernel,
linux-mediatek, linux-renesas-soc
On 07/02/2018 01:33 PM, Lorenzo Pieralisi wrote:
>>>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>>>
>>>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>>>> [ 1.235496] Modules linked in:
>>>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>>>> [ 1.271002] sp : ffff000008da39e0
>>>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>>>> [ 1.361056] Call trace:
>>>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>>>> [ 1.397269] __device_attach+0xc4/0x12c
>>>>> [ 1.401107] device_initial_probe+0x10/0x18
>>>>> [ 1.405292] bus_probe_device+0x90/0x98
>>>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>>>> [ 1.413756] process_one_work+0x12c/0x29c
>>>>> [ 1.417768] worker_thread+0x200/0x3fc
>>>>> [ 1.421522] kthread+0x108/0x134
>>>>> [ 1.424755] ret_from_fork+0x10/0x18
>>>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>>>
>>>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>>>> the probe was retried, finally causing the BUG due to trying to remap
>>>>> already remapped pages.
>>>>>
>>>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>>>> automagically on any probe failure.
>>>>>
>>>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>>>> drivers that have probably copied the bad example...
>>>>>
>>>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>> Cc: stable@vger.kernel.org
>>>>
>>>> Let me know if you want me to take this, Lorenzo, otherwise:
>>>> s/pci: fix/PCI: Fix/ and
>>>>
>>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>>
>>> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
>>> more so given the stable tag (and I think that each "Fixes" tag should
>>> be self-contained),
>>
>> It cannot be self-contained because it'll depend on the initial
>> commit adding devm_pci_remap_iobase(). If you mean finding the
>> earliest broken driver and introduce the deviec managed API while
>> fixing it and then make use of that
>> API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
OK! :-)
>>> merging it as-is would give Greg (and us) a
>>> headache when it comes to backporting it.
>>
>> The patch interdependency would give him headache too, and I was
>> hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
I think the -stable maintainers are actively looking at the Fixes: tags
these days, not only at stable@vger.kernel.org. I can do thsat
>>> Honestly I think it is best to split it up and send it for v4.19 but
>>> I am happy to hear other options.
>>
>> I disagree about 4.19. The R-Car PCIe situation is as follows:
>> given me missing to get the PHY driver merged into 4.18 (and the
>> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
>> have PCIe not working (if he doesn't refer to the PHY driver in DT)
>> or encounter a kernel BUG (if he does refer to the PHY driver), thus
s/driver/device/, of course. :-)
>> I'd like this BUG to be fixed in 4.18 time frame...
>
> We shall try, please let me know if you are able to respin asap,
> we already have a bunch of fixes queued.
I can probably try -- despite I'm on vacations and the football
championship is still going on. :-)
> Thanks for putting it together,
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: [PATCH] pci: fix I/O space page leak
@ 2018-07-02 19:40 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-07-02 19:40 UTC (permalink / raw)
To: Lorenzo Pieralisi
Cc: Thomas Petazzoni, Rob Herring, Joao Pinto, linux-pci,
Linus Walleij, linux-renesas-soc, Matthias Brugger, Ryder Lee,
Bjorn Helgaas, Tanmay Inamdar, Jingoo Han, Bjorn Helgaas,
linux-mediatek, linux-arm-kernel
On 07/02/2018 01:33 PM, Lorenzo Pieralisi wrote:
>>>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>>>
>>>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>>>> [ 1.235496] Modules linked in:
>>>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>>>> [ 1.271002] sp : ffff000008da39e0
>>>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>>>> [ 1.361056] Call trace:
>>>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>>>> [ 1.397269] __device_attach+0xc4/0x12c
>>>>> [ 1.401107] device_initial_probe+0x10/0x18
>>>>> [ 1.405292] bus_probe_device+0x90/0x98
>>>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>>>> [ 1.413756] process_one_work+0x12c/0x29c
>>>>> [ 1.417768] worker_thread+0x200/0x3fc
>>>>> [ 1.421522] kthread+0x108/0x134
>>>>> [ 1.424755] ret_from_fork+0x10/0x18
>>>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>>>
>>>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>>>> the probe was retried, finally causing the BUG due to trying to remap
>>>>> already remapped pages.
>>>>>
>>>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>>>> automagically on any probe failure.
>>>>>
>>>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>>>> drivers that have probably copied the bad example...
>>>>>
>>>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>> Cc: stable@vger.kernel.org
>>>>
>>>> Let me know if you want me to take this, Lorenzo, otherwise:
>>>> s/pci: fix/PCI: Fix/ and
>>>>
>>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>>
>>> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
>>> more so given the stable tag (and I think that each "Fixes" tag should
>>> be self-contained),
>>
>> It cannot be self-contained because it'll depend on the initial
>> commit adding devm_pci_remap_iobase(). If you mean finding the
>> earliest broken driver and introduce the deviec managed API while
>> fixing it and then make use of that
>> API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
OK! :-)
>>> merging it as-is would give Greg (and us) a
>>> headache when it comes to backporting it.
>>
>> The patch interdependency would give him headache too, and I was
>> hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
I think the -stable maintainers are actively looking at the Fixes: tags
these days, not only at stable@vger.kernel.org. I can do thsat
>>> Honestly I think it is best to split it up and send it for v4.19 but
>>> I am happy to hear other options.
>>
>> I disagree about 4.19. The R-Car PCIe situation is as follows:
>> given me missing to get the PHY driver merged into 4.18 (and the
>> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
>> have PCIe not working (if he doesn't refer to the PHY driver in DT)
>> or encounter a kernel BUG (if he does refer to the PHY driver), thus
s/driver/device/, of course. :-)
>> I'd like this BUG to be fixed in 4.18 time frame...
>
> We shall try, please let me know if you are able to respin asap,
> we already have a bunch of fixes queued.
I can probably try -- despite I'm on vacations and the football
championship is still going on. :-)
> Thanks for putting it together,
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
* [PATCH] pci: fix I/O space page leak
@ 2018-07-02 19:40 ` Sergei Shtylyov
0 siblings, 0 replies; 37+ messages in thread
From: Sergei Shtylyov @ 2018-07-02 19:40 UTC (permalink / raw)
To: linux-arm-kernel
On 07/02/2018 01:33 PM, Lorenzo Pieralisi wrote:
>>>>> When testing the R-Car PCIe driver on the Condor board, I noticed that iff
>>>>> I left the PCIe PHY driver disabled, the kernel crashed with this BUG:
>>>>>
>>>>> [ 1.225819] kernel BUG at lib/ioremap.c:72!
>>>>> [ 1.230007] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
>>>>> [ 1.235496] Modules linked in:
>>>>> [ 1.238561] CPU: 0 PID: 39 Comm: kworker/0:1 Not tainted 4.17.0-dirty #1092
>>>>> [ 1.245526] Hardware name: Renesas Condor board based on r8a77980 (DT)
>>>>> [ 1.252075] Workqueue: events deferred_probe_work_func
>>>>> [ 1.257220] pstate: 80000005 (Nzcv daif -PAN -UAO)
>>>>> [ 1.262024] pc : ioremap_page_range+0x370/0x3c8
>>>>> [ 1.266558] lr : ioremap_page_range+0x40/0x3c8
>>>>> [ 1.271002] sp : ffff000008da39e0
>>>>> [ 1.274317] x29: ffff000008da39e0 x28: 00e8000000000f07
>>>>> [ 1.279636] x27: ffff7dfffee00000 x26: 0140000000000000
>>>>> [ 1.284954] x25: ffff7dfffef00000 x24: 00000000000fe100
>>>>> [ 1.290272] x23: ffff80007b906000 x22: ffff000008ab8000
>>>>> [ 1.295590] x21: ffff000008bb1d58 x20: ffff7dfffef00000
>>>>> [ 1.300909] x19: ffff800009c30fb8 x18: 0000000000000001
>>>>> [ 1.306226] x17: 00000000000152d0 x16: 00000000014012d0
>>>>> [ 1.311544] x15: 0000000000000000 x14: 0720072007200720
>>>>> [ 1.316862] x13: 0720072007200720 x12: 0720072007200720
>>>>> [ 1.322180] x11: 0720072007300730 x10: 00000000000000ae
>>>>> [ 1.327498] x9 : 0000000000000000 x8 : ffff7dffff000000
>>>>> [ 1.332816] x7 : 0000000000000000 x6 : 0000000000000100
>>>>> [ 1.338134] x5 : 0000000000000000 x4 : 000000007b906000
>>>>> [ 1.343452] x3 : ffff80007c61a880 x2 : ffff7dfffeefffff
>>>>> [ 1.348770] x1 : 0000000040000000 x0 : 00e80000fe100f07
>>>>> [ 1.354090] Process kworker/0:1 (pid: 39, stack limit = 0x (ptrval))
>>>>> [ 1.361056] Call trace:
>>>>> [ 1.363504] ioremap_page_range+0x370/0x3c8
>>>>> [ 1.367695] pci_remap_iospace+0x7c/0xac
>>>>> [ 1.371624] pci_parse_request_of_pci_ranges+0x13c/0x190
>>>>> [ 1.376945] rcar_pcie_probe+0x4c/0xb04
>>>>> [ 1.380786] platform_drv_probe+0x50/0xbc
>>>>> [ 1.384799] driver_probe_device+0x21c/0x308
>>>>> [ 1.389072] __device_attach_driver+0x98/0xc8
>>>>> [ 1.393431] bus_for_each_drv+0x54/0x94
>>>>> [ 1.397269] __device_attach+0xc4/0x12c
>>>>> [ 1.401107] device_initial_probe+0x10/0x18
>>>>> [ 1.405292] bus_probe_device+0x90/0x98
>>>>> [ 1.409130] deferred_probe_work_func+0xb0/0x150
>>>>> [ 1.413756] process_one_work+0x12c/0x29c
>>>>> [ 1.417768] worker_thread+0x200/0x3fc
>>>>> [ 1.421522] kthread+0x108/0x134
>>>>> [ 1.424755] ret_from_fork+0x10/0x18
>>>>> [ 1.428334] Code: f9004ba2 54000080 aa0003fb 17ffff48 (d4210000)
>>>>>
>>>>> It turned out that pci_remap_iospace() wasn't undone when the driver's
>>>>> probe failed, and since devm_phy_optional_get() returned -EPROBE_DEFER,
>>>>> the probe was retried, finally causing the BUG due to trying to remap
>>>>> already remapped pages.
>>>>>
>>>>> The most feasible solution seems to introduce devm_pci_remap_iospace()
>>>>> and call it instead of pci_remap_iospace(), so that the pages get unmapped
>>>>> automagically on any probe failure.
>>>>>
>>>>> And while fixing pci_parse_request_of_pci_ranges(), aslo fix the other
>>>>> drivers that have probably copied the bad example...
>>>>>
>>>>> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for use by other drivers")
>>>>> Fixes: cbce7900598c ("PCI: designware: Make driver arch-agnostic")
>>>>> Fixes: 8c39d710363c ("PCI: aardvark: Add Aardvark PCI host controller driver")
>>>>> Fixes: d3c68e0a7e34 ("PCI: faraday: Add Faraday Technology FTPCI100 PCI Host Bridge driver")
>>>>> Fixes: 68a15eb7bd0c ("PCI: v3-semi: Add V3 Semiconductor PCI host driver")
>>>>> Fixes: b7e78170efd4 ("PCI: versatile: Add DT-based ARM Versatile PB PCIe host driver")
>>>>> Fixes: 5f6b6ccdbe1c ("PCI: xgene: Add APM X-Gene PCIe driver")
>>>>> Fixes: 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller support")
>>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>> Cc: stable at vger.kernel.org
>>>>
>>>> Let me know if you want me to take this, Lorenzo, otherwise:
>>>> s/pci: fix/PCI: Fix/ and
>>>>
>>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>>
>>> Thank you Bjorn, yes it could go in as a fix but IMO it has to be split,
>>> more so given the stable tag (and I think that each "Fixes" tag should
>>> be self-contained),
>>
>> It cannot be self-contained because it'll depend on the initial
>> commit adding devm_pci_remap_iobase(). If you mean finding the
>> earliest broken driver and introduce the deviec managed API while
>> fixing it and then make use of that
>> API in the subsequent patches, that surely can be done.
>
> Yes I think that's the best course of action.
OK! :-)
>>> merging it as-is would give Greg (and us) a
>>> headache when it comes to backporting it.
>>
>> The patch interdependency would give him headache too, and I was
>> hoping to relieve those with the monilitic patch. :-)
>
> The problem is that if any of the fixes has to be reverted we have
> to revert the whole thing instead of just the problematic patch,
> which, given that we are sending this to stable kernels may easily
> turn out quite complicated.
>
> So, I would add the new API along with the earliest broken driver
> and mark it for stable.
>
> In the same thread, add all other fixes (one per patch) without the
> stable tag. When the first fix gets merged into the mainline (and
> consequently goes to stable) we can send the stable backports for the
> remainder of fixes.
>
> How does that sound ?
I think the -stable maintainers are actively looking at the Fixes: tags
these days, not only at stable at vger.kernel.org. I can do thsat
>>> Honestly I think it is best to split it up and send it for v4.19 but
>>> I am happy to hear other options.
>>
>> I disagree about 4.19. The R-Car PCIe situation is as follows:
>> given me missing to get the PHY driver merged into 4.18 (and the
>> gen3 PCIe stuff successfully merged into 4.18), the user is bound to
>> have PCIe not working (if he doesn't refer to the PHY driver in DT)
>> or encounter a kernel BUG (if he does refer to the PHY driver), thus
s/driver/device/, of course. :-)
>> I'd like this BUG to be fixed in 4.18 time frame...
>
> We shall try, please let me know if you are able to respin asap,
> we already have a bunch of fixes queued.
I can probably try -- despite I'm on vacations and the football
championship is still going on. :-)
> Thanks for putting it together,
> Lorenzo
MBR, Sergei
^ permalink raw reply [flat|nested] 37+ messages in thread
end of thread, other threads:[~2018-07-02 19:40 UTC | newest]
Thread overview: 37+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-20 17:51 [PATCH] pci: fix I/O space page leak Sergei Shtylyov
2018-06-20 17:51 ` Sergei Shtylyov
2018-06-20 17:51 ` Sergei Shtylyov
2018-06-20 19:36 ` Jingoo Han
2018-06-20 19:36 ` Jingoo Han
2018-06-20 19:36 ` Jingoo Han
2018-06-20 19:36 ` Jingoo Han
2018-06-21 6:55 ` Thomas Petazzoni
2018-06-21 6:55 ` Thomas Petazzoni
2018-06-21 6:55 ` Thomas Petazzoni
2018-06-21 6:55 ` Thomas Petazzoni
2018-06-26 7:36 ` Linus Walleij
2018-06-26 7:36 ` Linus Walleij
2018-06-26 7:36 ` Linus Walleij
2018-06-26 7:36 ` Linus Walleij
2018-06-28 13:22 ` Bjorn Helgaas
2018-06-28 13:22 ` Bjorn Helgaas
2018-06-28 13:22 ` Bjorn Helgaas
2018-06-28 13:22 ` Bjorn Helgaas
2018-06-28 14:26 ` Lorenzo Pieralisi
2018-06-28 14:26 ` Lorenzo Pieralisi
2018-06-28 14:26 ` Lorenzo Pieralisi
2018-06-30 10:37 ` Sergei Shtylyov
2018-06-30 10:37 ` Sergei Shtylyov
2018-06-30 10:37 ` Sergei Shtylyov
2018-07-02 10:33 ` Lorenzo Pieralisi
2018-07-02 10:33 ` Lorenzo Pieralisi
2018-07-02 10:33 ` Lorenzo Pieralisi
2018-07-02 11:08 ` Geert Uytterhoeven
2018-07-02 11:08 ` Geert Uytterhoeven
2018-07-02 11:08 ` Geert Uytterhoeven
2018-07-02 14:12 ` Lorenzo Pieralisi
2018-07-02 14:12 ` Lorenzo Pieralisi
2018-07-02 14:12 ` Lorenzo Pieralisi
2018-07-02 19:40 ` Sergei Shtylyov
2018-07-02 19:40 ` Sergei Shtylyov
2018-07-02 19:40 ` Sergei Shtylyov
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.