From: Oliver Neukum <oneukum@suse.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Korneliusz Osmenda <korneliuszo@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Guard pci_create_sysfs_dev_files with atomic value
Date: Thu, 16 Mar 2023 10:23:54 +0100 [thread overview]
Message-ID: <106b5618-908f-becc-6eb3-75ef136a48e4@suse.com> (raw)
In-Reply-To: <20230316091540.494366-1-alexander.stein@ew.tq-group.com>
On 16.03.23 10:15, Alexander Stein wrote:
> From: Korneliusz Osmenda <korneliuszo@gmail.com>
>
> On Gateworks Ventana there is a number of PCI devices and:
> - imx6_pcie_probe takes longer than start of late init
> - pci_sysfs_init sets up flag sysfs_initialized
> - pci_sysfs_init initializes already found devices
> - imx6_pcie_probe tries to reinitialize device
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215515
>
> Signed-off-by: Korneliusz Osmenda <korneliuszo@gmail.com>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> drivers/pci/pci-sysfs.c | 6 ++++++
> include/linux/pci.h | 2 ++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
> index dd0d9d9bc509..998e44716b6f 100644
> --- a/drivers/pci/pci-sysfs.c
> +++ b/drivers/pci/pci-sysfs.c
> @@ -1497,6 +1497,9 @@ int __must_check pci_create_sysfs_dev_files(struct pci_dev *pdev)
> if (!sysfs_initialized)
> return -EACCES;
>
> + if (atomic_cmpxchg(&pdev->sysfs_init_cnt, 0, 1) == 1)
> + return 0; /* already added */
> +
> return pci_create_resource_files(pdev);
This is very likely a bug. You are returning an error in the error
case. Yet the flag stays. And simply resetting it in the error case
would be a race. There is something fishy in that design.
Regards
Oliver
next prev parent reply other threads:[~2023-03-16 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:15 [PATCH v2 1/1] Guard pci_create_sysfs_dev_files with atomic value Alexander Stein
2023-03-16 9:18 ` Alexander Stein
2023-03-16 9:23 ` Oliver Neukum [this message]
2023-03-16 9:33 ` Alexander Stein
2023-03-16 11:17 ` Oliver Neukum
2023-03-16 11:58 ` Alexander Stein
2023-03-16 12:23 ` Oliver Neukum
2023-03-16 13:16 ` Alexander Stein
2023-03-16 14:01 ` Oliver Neukum
2023-03-16 15:00 ` Alexander Stein
2023-03-21 9:09 ` Oliver Neukum
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=106b5618-908f-becc-6eb3-75ef136a48e4@suse.com \
--to=oneukum@suse.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=bhelgaas@google.com \
--cc=korneliuszo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox