From: Matthew Wood <thepacketgeek@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kbusch@kernel.org, Nikita Vetoshkin <nekto0n@meta.com>
Subject: [PATCH 4/5] PCI/sysfs: Use user config accessors for link attributes
Date: Sat, 24 Oct 2026 17:08:32 -0700 [thread overview]
Message-ID: <20261025000836.58294-5-thepacketgeek@gmail.com> (raw)
In-Reply-To: <20261025000836.58294-1-thepacketgeek@gmail.com>
max_link_width, current_link_speed and current_link_width read the PCIe
Link Capabilities and Link Status registers with the kernel config
accessors. Those don't check block_cfg_access so a read that races
with a reset goes to the device mid-reset and can fail or return a bogus
value.
Use pcie_capability_user_read_{word,dword}() instead so the read waits for
any pci_cfg_access_lock() holder (e.g. pci_reset_function()) to finish. For
max_link_width, this means inlining the pcie_get_width_cap() logic
instead of creating an additional helper with this single calling location.
Signed-off-by: Matthew Wood <thepacketgeek@gmail.com>
Tested-by: Nikita Vetoshkin <nekto0n@meta.com>
---
drivers/pci/pci-sysfs.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
index b37a285d717d..a272f8583a8f 100644
--- a/drivers/pci/pci-sysfs.c
+++ b/drivers/pci/pci-sysfs.c
@@ -208,14 +208,16 @@ static ssize_t max_link_width_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
struct pci_dev *pdev = to_pci_dev(dev);
- ssize_t ret;
+ u32 lnkcap;
/* We read PCI_EXP_LNKCAP, so we need the device to be accessible. */
pci_config_pm_runtime_get(pdev);
- ret = sysfs_emit(buf, "%u\n", pcie_get_width_cap(pdev));
+ pcie_capability_user_read_dword(pdev, PCI_EXP_LNKCAP, &lnkcap);
pci_config_pm_runtime_put(pdev);
- return ret;
+ return sysfs_emit(buf, "%u\n", lnkcap ?
+ FIELD_GET(PCI_EXP_LNKCAP_MLW, lnkcap) :
+ PCIE_LNK_WIDTH_UNKNOWN);
}
static DEVICE_ATTR_RO(max_link_width);
@@ -228,7 +230,8 @@ static ssize_t current_link_speed_show(struct device *dev,
enum pci_bus_speed speed;
pci_config_pm_runtime_get(pci_dev);
- err = pcie_capability_read_word(pci_dev, PCI_EXP_LNKSTA, &linkstat);
+ err = pcie_capability_user_read_word(pci_dev, PCI_EXP_LNKSTA,
+ &linkstat);
pci_config_pm_runtime_put(pci_dev);
if (err)
@@ -248,7 +251,8 @@ static ssize_t current_link_width_show(struct device *dev,
int err;
pci_config_pm_runtime_get(pci_dev);
- err = pcie_capability_read_word(pci_dev, PCI_EXP_LNKSTA, &linkstat);
+ err = pcie_capability_user_read_word(pci_dev, PCI_EXP_LNKSTA,
+ &linkstat);
pci_config_pm_runtime_put(pci_dev);
if (err)
--
2.53.0-Meta
next prev parent reply other threads:[~2026-10-25 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 0:08 [PATCH 0/5] PCI/sysfs: Wait for config access lock in sysfs attributes Matthew Wood
2026-10-25 0:08 ` [PATCH 1/5] PCI: Add disconnected device checks to user config reads Matthew Wood
2026-10-25 0:08 ` [PATCH 2/5] PCI/sysfs: Use user config accessors for bus number attributes Matthew Wood
2026-10-26 15:00 ` Keith Busch
2026-10-25 0:08 ` [PATCH 3/5] PCI: Add pcie_capability_user_read_{word,dword}() Matthew Wood
2026-10-26 15:20 ` Keith Busch
2026-10-25 0:08 ` Matthew Wood [this message]
2026-10-26 15:21 ` [PATCH 4/5] PCI/sysfs: Use user config accessors for link attributes Keith Busch
2026-10-25 0:08 ` [PATCH 5/5] PCI/sysfs: Use user config accessors for serial_number Matthew Wood
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=20261025000836.58294-5-thepacketgeek@gmail.com \
--to=thepacketgeek@gmail.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nekto0n@meta.com \
/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
all inboxes | Powered by JetHome®