From: "Pali Rohár" <pali@kernel.org>
To: Koen Vandeputte <koen.vandeputte@citymesh.com>
Cc: "Petr Štetiar" <ynezz@true.cz>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Yinghai Lu" <yinghai@kernel.org>
Subject: Re: PCI: Race condition in pci_create_sysfs_dev_files
Date: Fri, 25 Jun 2021 13:54:02 +0200 [thread overview]
Message-ID: <20210625115402.jwga35xmknmo4vdk@pali> (raw)
In-Reply-To: <cd4812f0-1de3-0582-936c-ba30906595af@citymesh.com>
Hello!
On Friday 25 June 2021 13:29:00 Koen Vandeputte wrote:
> Hi all,
>
>
> Adding some more info regarding this issue:
>
> I've cooked up this simple patch to get some more info:
>
>
> Index: linux-5.10.44/drivers/pci/pci-sysfs.c
> ===================================================================
> --- linux-5.10.44.orig/drivers/pci/pci-sysfs.c
> +++ linux-5.10.44/drivers/pci/pci-sysfs.c
> @@ -1335,6 +1335,8 @@ int __must_check pci_create_sysfs_dev_fi
> int rom_size;
> struct bin_attribute *attr;
>
> + dump_stack();
> +
> if (!sysfs_initialized)
> return -EACCES;
>
>
> Which shows this:
>
>
> [ 1.847384] Key type .fscrypt registered
> [ 1.854288] pci 0000:01:00.0: PCI bridge to [bus 02-05]
> [ 1.859242] Key type fscrypt-provisioning registered
> [ 1.863252] pci 0000:01:00.0: bridge window [mem 0x01100000-0x011fffff]
> [ 1.874096] Key type encrypted registered
> [ 1.879290] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
> [ 1.879306] pci 0000:00:00.0: bridge window [mem 0x01100000-0x012fffff]
>
> --> patch kicking in here showing first creation now
>
> [ 1.879346] CPU: 1 PID: 7 Comm: kworker/u4:0 Not tainted 5.10.44 #0
> [ 1.913354] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [ 1.919908] Workqueue: events_unbound async_run_entry_fn
> [ 1.925255] [<8010d5e0>] (unwind_backtrace) from [<801099f0>]
> (show_stack+0x10/0x14)
> [ 1.933008] [<801099f0>] (show_stack) from [<804ab92c>]
> (dump_stack+0x94/0xa8)
> [ 1.940249] [<804ab92c>] (dump_stack) from [<804ea96c>]
> (pci_create_sysfs_dev_files+0x10/0x28c)
> [ 1.948969] [<804ea96c>] (pci_create_sysfs_dev_files) from [<804dc648>]
> (pci_bus_add_device+0x20/0x84)
> [ 1.958287] [<804dc648>] (pci_bus_add_device) from [<804dc6d8>]
> (pci_bus_add_devices+0x2c/0x70)
> [ 1.966996] [<804dc6d8>] (pci_bus_add_devices) from [<804dffc8>]
> (pci_host_probe+0x40/0x94)
> [ 1.975362] [<804dffc8>] (pci_host_probe) from [<804fd5f0>]
> (dw_pcie_host_init+0x1c0/0x3fc)
> [ 1.983720] [<804fd5f0>] (dw_pcie_host_init) from [<804fdcb0>]
> (imx6_pcie_probe+0x358/0x63c)
> [ 1.992179] [<804fdcb0>] (imx6_pcie_probe) from [<8054c79c>]
> (platform_drv_probe+0x48/0x98)
> [ 2.000542] [<8054c79c>] (platform_drv_probe) from [<8054a9fc>]
> (really_probe+0xfc/0x4dc)
> [ 2.008732] [<8054a9fc>] (really_probe) from [<8054b0bc>]
> (driver_probe_device+0x5c/0xb4)
> [ 2.016916] [<8054b0bc>] (driver_probe_device) from [<8054b1bc>]
> (__driver_attach_async_helper+0xa8/0xac)
> [ 2.026497] [<8054b1bc>] (__driver_attach_async_helper) from [<8014beec>]
> (async_run_entry_fn+0x44/0x108)
> [ 2.036082] [<8014beec>] (async_run_entry_fn) from [<80141b64>]
> (process_one_work+0x1d8/0x43c)
> [ 2.044704] [<80141b64>] (process_one_work) from [<80141e2c>]
> (worker_thread+0x64/0x5b0)
> [ 2.052802] [<80141e2c>] (worker_thread) from [<80147698>]
> (kthread+0x148/0x14c)
> [ 2.060207] [<80147698>] (kthread) from [<80100148>]
> (ret_from_fork+0x14/0x2c)
> [ 2.067433] Exception stack(0x81075fb0 to 0x81075ff8)
> [ 2.072493] 5fa0: 00000000 00000000
> 00000000 00000000
> [ 2.080678] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> [ 2.088864] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
>
> --> getting called again .. different caller this time .. seems unimportant
> ?
>
> [ 2.095490] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.44 #0
> [ 2.095924] pcieport 0000:00:00.0: PME: Signaling with IRQ 307
> [ 2.101510] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [ 2.113883] [<8010d5e0>] (unwind_backtrace) from [<801099f0>]
> (show_stack+0x10/0x14)
> [ 2.121638] [<801099f0>] (show_stack) from [<804ab92c>]
> (dump_stack+0x94/0xa8)
> [ 2.128875] [<804ab92c>] (dump_stack) from [<804ea96c>]
> (pci_create_sysfs_dev_files+0x10/0x28c)
> [ 2.137588] [<804ea96c>] (pci_create_sysfs_dev_files) from [<80b1b920>]
> (pci_sysfs_init+0x34/0x54)
> [ 2.146559] [<80b1b920>] (pci_sysfs_init) from [<80101820>]
> (do_one_initcall+0x54/0x1e8)
> [ 2.154667] [<80101820>] (do_one_initcall) from [<80b01108>]
> (kernel_init_freeable+0x23c/0x290)
> [ 2.163386] [<80b01108>] (kernel_init_freeable) from [<80837e3c>]
> (kernel_init+0x8/0x118)
> [ 2.171578] [<80837e3c>] (kernel_init) from [<80100148>]
> (ret_from_fork+0x14/0x2c)
> [ 2.179151] Exception stack(0x81053fb0 to 0x81053ff8)
> [ 2.184210] 3fa0: 00000000 00000000
> 00000000 00000000
> [ 2.192393] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> [ 2.200575] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000
>
> --> And then finally, the error occurs as it's already been added before.
> same cpu and same PID trying to add the same stuff again to sysfs
This just proves that you have hit this race condition.
> [ 2.207200] CPU: 1 PID: 7 Comm: kworker/u4:0 Not tainted 5.10.44 #0
> [ 2.207263] sysfs: cannot create duplicate filename
> '/devices/platform/soc/1ffc000.pcie/pci0000:00/0000:00:00.0/config' <------
> [ 2.213478] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [ 2.230798] Workqueue: events_unbound async_run_entry_fn
> [ 2.236129] [<8010d5e0>] (unwind_backtrace) from [<801099f0>]
> (show_stack+0x10/0x14)
> [ 2.243882] [<801099f0>] (show_stack) from [<804ab92c>]
> (dump_stack+0x94/0xa8)
> [ 2.251118] [<804ab92c>] (dump_stack) from [<804ea96c>]
> (pci_create_sysfs_dev_files+0x10/0x28c)
> [ 2.259837] [<804ea96c>] (pci_create_sysfs_dev_files) from [<804dc648>]
> (pci_bus_add_device+0x20/0x84)
> [ 2.269153] [<804dc648>] (pci_bus_add_device) from [<804dc6d8>]
> (pci_bus_add_devices+0x2c/0x70)
> [ 2.277861] [<804dc6d8>] (pci_bus_add_devices) from [<804dc70c>]
> (pci_bus_add_devices+0x60/0x70)
> [ 2.286656] [<804dc70c>] (pci_bus_add_devices) from [<804dffc8>]
> (pci_host_probe+0x40/0x94)
> [ 2.295018] [<804dffc8>] (pci_host_probe) from [<804fd5f0>]
> (dw_pcie_host_init+0x1c0/0x3fc)
> [ 2.303377] [<804fd5f0>] (dw_pcie_host_init) from [<804fdcb0>]
> (imx6_pcie_probe+0x358/0x63c)
> [ 2.311832] [<804fdcb0>] (imx6_pcie_probe) from [<8054c79c>]
> (platform_drv_probe+0x48/0x98)
> [ 2.320196] [<8054c79c>] (platform_drv_probe) from [<8054a9fc>]
> (really_probe+0xfc/0x4dc)
> [ 2.328382] [<8054a9fc>] (really_probe) from [<8054b0bc>]
> (driver_probe_device+0x5c/0xb4)
> [ 2.336567] [<8054b0bc>] (driver_probe_device) from [<8054b1bc>]
> (__driver_attach_async_helper+0xa8/0xac)
> [ 2.346145] [<8054b1bc>] (__driver_attach_async_helper) from [<8014beec>]
> (async_run_entry_fn+0x44/0x108)
> [ 2.355727] [<8014beec>] (async_run_entry_fn) from [<80141b64>]
> (process_one_work+0x1d8/0x43c)
> [ 2.364350] [<80141b64>] (process_one_work) from [<80141e2c>]
> (worker_thread+0x64/0x5b0)
> [ 2.372449] [<80141e2c>] (worker_thread) from [<80147698>]
> (kthread+0x148/0x14c)
> [ 2.379853] [<80147698>] (kthread) from [<80100148>]
> (ret_from_fork+0x14/0x2c)
> [ 2.387077] Exception stack(0x81075fb0 to 0x81075ff8)
> [ 2.392134] 5fa0: 00000000 00000000
> 00000000 00000000
> [ 2.400317] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> [ 2.408498] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
>
>
>
> Any idea?
>
> Thanks,
>
> Koen
>
It is same race condition which I described in the first email of this
email thread. I described exactly when it happens. I'm not able to
trigger it with new kernels but as we know race conditions are hard to
trigger...
So result is that we know about it, just fix is not ready yet as it is
not easy to fix it.
Krzysztof has been working on fixing it, so maybe can provide an
update...
next prev parent reply other threads:[~2021-06-25 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 11:04 PCI: Race condition in pci_create_sysfs_dev_files Pali Rohár
2020-08-14 8:08 ` Pali Rohár
2020-09-09 11:28 ` Pali Rohár
2020-10-05 8:20 ` Pali Rohár
2020-10-05 13:54 ` Bjorn Helgaas
2020-10-06 22:22 ` Bjorn Helgaas
2020-10-07 1:47 ` Oliver O'Halloran
2020-10-07 8:14 ` Pali Rohár
2020-10-07 16:14 ` Bjorn Helgaas
2020-10-08 19:59 ` Bjorn Helgaas
2020-10-09 8:08 ` Pali Rohár
2020-11-04 16:29 ` Pali Rohár
2020-11-15 6:19 ` Krzysztof Wilczyński
2020-11-15 12:10 ` Pali Rohár
2020-10-07 8:12 ` Pali Rohár
2021-04-07 14:25 ` Petr Štetiar
2021-04-07 14:51 ` Pali Rohár
2021-04-07 15:30 ` Petr Štetiar
2021-06-25 11:29 ` Koen Vandeputte
2021-06-25 11:54 ` Pali Rohár [this message]
2021-10-13 6:18 ` Dexuan-Linux Cui
2021-11-18 3:09 ` Krzysztof Wilczyński
2021-11-18 3:42 ` Dexuan Cui
2020-11-04 16:46 ` Pali Rohár
2021-04-07 14:41 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210625115402.jwga35xmknmo4vdk@pali \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=koen.vandeputte@citymesh.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=yinghai@kernel.org \
--cc=ynezz@true.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.