PCI: Convert all dynamic sysfs attributes to static
Subsystems (3)
v6 cover PCI: Convert all dynamic sysfs attributes to static
Hello,
This series converts every dynamically allocated PCI sysfs attribute to a static const definition. After the full series, pci_sysfs_init() and sysfs_initialized are gone, and every sysfs file is created by the driver model at device_add() time.
Currently, the PCI resource files (resourceN, resourceN_wc) and the legacy bus files (legacy_io, legacy_mem) are created dynamically from two unsynchronised paths:
Path A: late_initcall
pci_sysfs_init (late_initcall)
sysfs_initialized = 1
for_each_pci_dev
pci_create_sysfs_dev_files
sysfs_create_bin_file (resourceN, resourceN_wc)
pci_find_next_bus
pci_create_legacy_files
sysfs_create_bin_file (legacy_io, legacy_mem)
Path B: device registration / hotplug
pci_bus_add_devices
pci_bus_add_device
pci_create_sysfs_dev_files
if (!sysfs_initialized) return <- only guard
sysfs_create_bin_file (resourceN, resourceN_wc)
On most ACPI systems this does not race because PCI enumeration completes at subsys_initcall time, before pci_sysfs_init() runs:
subsys_initcall (level 4):
acpi_pci_root_add
pci_bus_add_device
pci_create_sysfs_dev_files
if (!sysfs_initialized) <- not yet set
return -EACCES
late_initcall (level 7):
pci_sysfs_init
sysfs_initialized = 1
for_each_pci_dev
pci_create_sysfs_dev_files <- creates the files, no race
On Devicetree platforms the host controller is a platform driver that probes via the driver model, often on a workqueue, and overlaps with the late_initcall:
CPU 0 (late_initcall) CPU 1 (driver probe)
--------------------------- ----------------------------
pci_sysfs_init()
sysfs_initialized = 1
for_each_pci_dev(pdev) pci_bus_add_device(pdev)
pci_create_sysfs_dev_files() pci_create_sysfs_dev_files()
sysfs_create_bin_file() sysfs_create_bin_file()
-> "duplicate filename"
The same happens on ACPI when probing is asynchronous (hv_pci on Azure, RISC-V with ACPI).
The duplicate causes sysfs_create_bin_file() to fail with -EEXIST. pci_create_resource_files() then calls pci_remove_resource_files() in its error unwind, tearing down files the other thread created and still references through pdev->res_attr[]. This has caused kernel panics on i.MX6 and boot failures on other platforms.
Several different fixes have been proposed over the years: reordering the sysfs_initialized assignment, adding locks, checking pci_dev_is_added(), setting pdev->res_attr[] to NULL after kfree (which only prevents a double-free on the teardown path, not the error unwind removing the other thread's files). None would address the root cause.
This has been reported a few times:
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/SY0P300MB04687548090B73E40AF97D8897B82@SY0P300MB0468.AUSP300.PROD.OUTLOOK.COM/
- https://lore.kernel.org/linux-pci/20230105174736.GA1154719@bhelgaas/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/20200716110423.xtfyb3n6tn5ixedh@pali/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://bugzilla.kernel.org/show_bug.cgi?id=215515
- https://bugzilla.kernel.org/show_bug.cgi?id=216888
With static attributes the driver model creates sysfs entries once per device at device_add() time, under the device lock, eliminating the late_initcall iteration and the race along with it.
Krzysztof
---
Changes in v5:
https://lore.kernel.org/linux-pci/[email protected]/
- Fixed commit message for patch 13, removing reference to pci_resource_flags() which was no longer changed there.
- Added a new patch (24) to move the BAR resource resize (ReBAR) support behind existing PCI mmap #ifdef guard, so that the code is not included on architectures that do not support resource resizing (i.e., Alpha, etc.).
Changes in v5:
https://lore.kernel.org/linux-pci/[email protected]/
- Added new Tested-by, Reviewed-by, and Acked-by tags.
- Used the existing _io function names in the static macro definitions, deferring the rename to the conversion commit where it belongs, to avoid a forward reference across commits. This was reported by Sashiko, see:
https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org?part=6
- Folded the __resource_resize_store() conversion into the main static attributes commit so the resize path is never broken between commits. This was reported by Sashiko, see:
https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org?part=6
https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org?part=7
- Dropped the unnecessary parentheses cleanup from the Alpha BAR index commit, as the line is replaced two commits later anyway, as per Ilpo Järvinen's feedback.
- Squashed the Alpha accessor macro and cleanup commits into one, using pci_resource_is_mem() directly instead of the intermediate pci_resource_flags() step, as per Ilpo Järvinen's feedback.
- Moved the raw literal conversion in pci_create_legacy_files() into the macro definition commit, so the macros and their usage are introduced together, as per Ilpo Järvinen's feedback.
- Removed unnecessary backslash line continuation from the ternary in pci_mmap_legacy_page_range().
- Kept pci_resource_len() for visibility checks instead of resource_assigned(). The static is_visible() callback runs at device_add() time during the PCI enumeration, before the pci_assign_unassigned_bus_resources() populates res->parent, as such, resource_assigned() returned false for every BAR, hiding all resource files. This is related to review feedback from Ilpo Järvinen.
Changes in v4:
https://lore.kernel.org/linux-pci/[email protected]/
- Added new Reviewed-by tags.
- Added pci_resource_is_io() and pci_resource_is_mem() helpers for resource type checks, replacing the open-coded bitwise flag tests in pci_mmap_resource(), pci_resource_io(), and Alpha's pci_mmap_resource(), as per Ilpo Järvinen's suggestion.
- Split the __pci_mmap_fits() cleanup into two patches. An overflow fix for zero-length BARs, which now includes a
Fixes: tag referencing the original Alpha PCI sysfs commit, and the WARN macro removal is a separate cleanup as per Ilpo Järvinen's suggestion.
- Added a missing Fixes: tag to the Alpha lockdown check, referencing the commit that added the check to the generic path but missed Alpha's implementation.
- Added PCI_LEGACY_IO_SIZE and PCI_LEGACY_MEM_SIZE macros to replace the raw literals used for legacy address space sizes. These are used in both Alpha's pci_mmap_legacy_page_range() and the static legacy attribute definitions, as per Ilpo Järvinen's suggestion.
- Replaced sysfs_update_groups() in the BAR resize path with sysfs_remove_groups() before the resize and sysfs_create_groups() after, restoring the original teardown before BAR resize ordering. This was reported by Sashiko, see:
https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org?part=7
- Defined pci_dev_resource_attr_groups as a NULL macro when HAVE_PCI_MMAP and ARCH_GENERIC_PCI_MMAP_RESOURCE are both absent, so the resize path compiles unconditionally without #ifdef guards in the function body. This was reported by Sashiko, see:
https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org?part=7
- Moved the pci_legacy_has_sparse() prototype into the patch that introduces the function, alongside the existing pci_adjust_legacy_attr() declaration, to fix a bisection issue where Alpha would warn on -Wmissing-prototypes. This was reported by Sashiko, see:
https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org?part=18
Changes in v3:
https://lore.kernel.org/linux-pci/[email protected]/
- Updated for modern kernel releases and expanded scope. The v2 only covered the generic resource files. This version also converts Alpha's sparse/dense resource files and the legacy bus attributes, removing pci_sysfs_init() entirely.
- Split the single macro definition into three distinct ones (per I/O, UC, and WC), to make sure that each carries only the callbacks its resource type needs.
- Updated to use the new .bin_size callback, as the attributes are const, to replace using a->size directly, which was not ideal. This required changes to pci_llseek_resource(), to ensure that it would work for device and bus-level attributes.
- Updated the __resource_resize_store() to include CAP_SYS_ADMIN capabilities check.
- Added the security_locked_down() check to Alpha's pci_mmap_resource(), to align with other architectures.
Changes in v2:
https://lore.kernel.org/linux-pci/[email protected]/
- Refactored code so that the macros, helpers and internal functions can be used to correctly leverage the read(), write() and mmap() callbacks rather than to use the .is_bin_visible() callback to set up sysfs objects internals as this is not supported.
- Refactored some if-statements to check for a resource flag first, and then call either arch_can_pci_mmap_io() or arch_can_pci_mmap_wc(), plus store result of testing for IORESOURCE_MEM and IORESOURCE_PREFETCH flags into a boolean variable, as per Bjorn Helgaas' suggestion.
- Renamed pci_read_resource_io() and pci_write_resource_io() callbacks so that these are not specifically tied to I/O BARs read() and write() operations also as per Bjorn Helgaas' suggestion.
- Updated style for code handling bitwise operations to match the style that is preferred as per Bjorn Helgaas' suggestion.
- Updated commit messages adding more details about the implementation as requested by Bjorn Helgaas.
Krzysztof Wilczyński (24):
PCI/sysfs: Use PCI resource accessor macros
PCI: Add pci_resource_is_io() and pci_resource_is_mem() helpers PCI/sysfs: Only allow supported resource types in I/O and MMIO helpers PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is
zero
PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() PCI/sysfs: Add static PCI resource attribute macros PCI/sysfs: Convert PCI resource files to static attributes PCI/sysfs: Warn about BAR resize failure in __resource_resize_store() PCI/sysfs: Add stubs for pci_{create,remove}_sysfs_dev_files() PCI/sysfs: Limit pci_sysfs_init() late_initcall compile scope alpha/PCI: Add security_locked_down() check to pci_mmap_resource() alpha/PCI: Use BAR index in sysfs attr->private instead of resource
pointer
alpha/PCI: Use PCI resource accessor macros
alpha/PCI: Fix __pci_mmap_fits() overflow for zero-length BARs alpha/PCI: Remove WARN from __pci_mmap_fits()
alpha/PCI: Add static PCI resource attribute macros alpha/PCI: Convert resource files to static attributes PCI/sysfs: Remove pci_{create,remove}_sysfs_dev_files()
PCI: Add macros for legacy I/O and memory address space sizes alpha/PCI: Compute legacy size in pci_mmap_legacy_page_range() PCI/sysfs: Add __weak pci_legacy_has_sparse() helper PCI/sysfs: Convert legacy I/O and memory attributes to static
definitions
PCI/sysfs: Remove pci_create_legacy_files() and pci_sysfs_init() PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
arch/alpha/include/asm/pci.h | 13 +- arch/alpha/kernel/pci-sysfs.c | 373 +++++++++++---------- arch/powerpc/include/asm/pci.h | 2 - drivers/pci/bus.c | 1 - drivers/pci/pci-sysfs.c | 575 +++++++++++++++++++-------------- drivers/pci/pci.h | 16 +- drivers/pci/probe.c | 6 - drivers/pci/remove.c | 3 - include/linux/pci.h | 39 ++- 9 files changed, 579 insertions(+), 449 deletions(-)
Signature · 1 line
2.54.0
PATCH v6 1/24 PCI/sysfs: Use PCI resource accessor macros
Replace direct pdev->resource[] accesses with pci_resource_n(), and pdev->resource[].flags accesses with pci_resource_flags().
No functional changes intended.
--- drivers/pci/pci-sysfs.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/pci/pci-sysfs.c +4 -4
@@ -177,7 +177,7 @@ static ssize_t resource_show(struct device *dev, struct device_attribute *attr, max =PCI_BRIDGE_RESOURCES ;for (i =0 ; i < max; i++) { -struct resource *res = &pci_dev->resource[i]; +struct resource *res =pci_resource_n (pci_dev, i);struct resource zerores = {};/* For backwards compatibility */
@@ -715,7 +715,7 @@ static ssize_t boot_vga_show(struct device *dev, struct device_attribute *attr,return sysfs_emit (buf,"%u\n" , (pdev == vga_dev));return sysfs_emit (buf,"%u\n" , - !!(pdev->resource[PCI_ROM_RESOURCE ].flags & + !!(pci_resource_flags (pdev,PCI_ROM_RESOURCE ) &IORESOURCE_ROM_SHADOW )); }static DEVICE_ATTR_RO (boot_vga);
@@ -1108,7 +1108,7 @@ static int pci_mmap_resource(struct kobject *kobj, const struct bin_attribute *astruct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj));int bar = (unsigned long )attr->private;enum pci_mmap_state mmap_type; -struct resource *res = &pdev->resource[bar]; +struct resource *res =pci_resource_n (pdev, bar);int ret; ret =security_locked_down (LOCKDOWN_PCI_ACCESS );
@@ -1312,7 +1312,7 @@ static int pci_create_resource_files(struct pci_dev *pdev) retval =pci_create_attr (pdev, i,0 );/* for prefetchable resources, create a WC mappable file */ if (!retval &&arch_can_pci_mmap_wc () && - pdev->resource[i].flags &IORESOURCE_PREFETCH ) +pci_resource_flags (pdev, i) &IORESOURCE_PREFETCH ) retval =pci_create_attr (pdev, i,1 );if (retval) {pci_remove_resource_files (pdev);
Signature · 1 line
2.54.0
PATCH v6 2/24 PCI: Add pci_resource_is_io() and pci_resource_is_mem() helpers
In reply to Krzysztof WilczyńskiAdd helpers to check whether a PCI resource is of I/O port or memory type. These replace the open-coded pci_resource_flags() with IORESOURCE_IO and IORESOURCE_MEM pattern used across the tree.
--- include/linux/pci.h | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+)
include/linux/pci.h +25 -0
@@ -2295,6 +2295,31 @@ int pci_iobar_pfn(struct pci_dev *pdev, int bar, struct vm_area_struct *vma);CONCATENATE (__pci_dev_for_each_res,COUNT_ARGS (__VA_ARGS__)) \ (dev, res, __VA_ARGS__) +/** +* pci_resource_is_io - check if a PCI resource is of I/O port type. +* @dev: PCI device to check. +* @resno: The resource number (BAR index) to check. +* +* Returns true if the resource type is I/O port. + */ +static inline bool pci_resource_is_io (const struct pci_dev *dev,int resno) +{ +return resource_type (pci_resource_n (dev, resno)) ==IORESOURCE_IO ; +} + +/** +* pci_resource_is_mem - check if a PCI resource is of memory type. +* @dev: PCI device to check. +* @resno: The resource number (BAR index) to check. +* +* Returns true if the resource type is memory, including +* prefetchable memory. +*/ +static inline bool pci_resource_is_mem (const struct pci_dev *dev,int resno) +{ +return resource_type (pci_resource_n (dev, resno)) ==IORESOURCE_MEM ; +} +/* * Similar to the helpers above, these manipulate per-pci_dev * driver-specific data. They are really just a wrapper around
Signature · 1 line
2.54.0
PATCH v6 3/24 PCI/sysfs: Only allow supported resource types in I/O and MMIO helpers
In reply to Krzysztof WilczyńskiCurrently, when the sysfs attributes for PCI resources are added dynamically, the resource access callbacks are only set when the underlying BAR type matches, using .read and .write for IORESOURCE_IO, and .mmap for IORESOURCE_MEM or IORESOURCE_IO with arch_can_pci_mmap_io() support. As such, when the callback is not set, the operation inherently fails.
After the conversion to static attributes, visibility callbacks will control which resource files appear for each BAR, but the callbacks themselves will always be set.
Thus, add a type check to pci_resource_io() and pci_mmap_resource() to return -EIO for an unsupported resource type.
Use the new pci_resource_is_io() and pci_resource_is_mem() helpers for the type checks, replacing the open-coded bitwise flag tests and also drop the local struct resource pointer in pci_mmap_resource().
--- drivers/pci/pci-sysfs.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/pci/pci-sysfs.c +10 -3
@@ -1108,20 +1108,24 @@ static int pci_mmap_resource(struct kobject *kobj, const struct bin_attribute *astruct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj));int bar = (unsigned long )attr->private;enum pci_mmap_state mmap_type; -struct resource *res =pci_resource_n (pdev, bar);int ret; ret =security_locked_down (LOCKDOWN_PCI_ACCESS );if (ret)return ret; -if (res->flags &IORESOURCE_MEM &&iomem_is_exclusive (res->start)) +if (!pci_resource_is_mem (pdev, bar) && + !(pci_resource_is_io (pdev, bar) &&arch_can_pci_mmap_io ())) +return -EIO ; + +if (pci_resource_is_mem (pdev, bar) && +iomem_is_exclusive (pci_resource_start (pdev, bar)))return -EINVAL ;if (!pci_mmap_fits (pdev, bar, vma,PCI_MMAP_SYSFS ))return -EINVAL ; - mmap_type = res->flags &IORESOURCE_MEM ? pci_mmap_mem : pci_mmap_io; + mmap_type =pci_resource_is_mem (pdev, bar) ? pci_mmap_mem : pci_mmap_io;return pci_mmap_resource_range (pdev, bar, vma, mmap_type, write_combine); }
@@ -1149,6 +1153,9 @@ static ssize_t pci_resource_io(struct file *filp, struct kobject *kobj,int bar = (unsigned long )attr->private;unsigned long port = off; +if (!pci_resource_is_io (pdev, bar)) +return -EIO ; + port +=pci_resource_start (pdev, bar);if (port >pci_resource_end (pdev, bar))
Signature · 1 line
2.54.0
PATCH v6 4/24 PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
In reply to Krzysztof WilczyńskiBoth legacy and resource attributes set .f_mapping = iomem_get_mapping, so the default generic_file_llseek() would consult iomem_inode for the file size, which knows nothing about the attribute. That is why this custom llseek callback exists.
Currently, the legacy and resource attributes have .size set at creation time, as such, using the attr->size is sufficient. However, the upcoming static resource attributes will have .size == 0 set, since they are const, and the .bin_size callback will be used to provide the real size to kernfs instead.
Thus, update pci_llseek_resource() to derive the file size from the BAR using pci_resource_len() instead of reading the attr->size directly.
The custom pci_llseek_resource() helper has been added in commit 24de09c16f97 ("PCI: Implement custom llseek for sysfs resource entries").
--- drivers/pci/pci-sysfs.c | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)
drivers/pci/pci-sysfs.c +12 -2
@@ -909,11 +909,21 @@ static const struct attribute_group pci_dev_config_attr_group = {*/ static __maybe_unused loff_t pci_llseek_resource (struct file *filep, -struct kobject *kobj__always_unused , +struct kobject *kobj,const struct bin_attribute *attr,loff_t offset,int whence) { -return fixed_size_llseek (filep, offset, whence, attr->size); +struct pci_dev *pdev; +int bar; + +if (attr->size) +return fixed_size_llseek (filep, offset, whence, attr->size); + + pdev =to_pci_dev (kobj_to_dev (kobj)); + bar = (unsigned long )attr->private; + +return fixed_size_llseek (filep, offset, whence, +pci_resource_len (pdev, bar)); }#ifdef HAVE_PCI_LEGACY
Signature · 1 line
2.54.0
Re: [PATCH v6 04/24] PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
Quoted 38 lines · Krzysztof Wilczyński
Both legacy and resource attributes set .f_mapping =
iomem_get_mapping, so the defaultgeneric_file_llseek()would consultiomem_inodefor the file size, which knows nothing about the attribute. That is why this custom llseek callback exists.Currently, the legacy and resource attributes have .size set at creation time, as such, using the
attr->sizeis sufficient. However, the upcoming static resource attributes will have .size == 0 set, since they are const, and the .bin_size callback will be used to provide the real size to kernfs instead.Thus, update
pci_llseek_resource()to derive the file size from the BAR usingpci_resource_len()instead of reading theattr->sizedirectly.The custom
pci_llseek_resource()helper has been added in commit24de09c16f97("PCI: Implement custom llseek for sysfs resource entries").Signed-off-by Krzysztof Wilczyński <[email protected]>--- drivers/pci/pci-sysfs.c | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)drivers/pci/pci-sysfs.c +2
-2@@ -909,11 +909,21 @@ static const struct attribute_group pci_dev_config_attr_group = {*/ static __maybe_unused loff_t pci_llseek_resource (struct file *filep, -struct kobject *kobj__always_unused , +struct kobject *kobj,const struct bin_attribute *attr,loff_t offset,int whence) { -return fixed_size_llseek (filep, offset, whence, attr->size); +struct pci_dev *pdev;
drivers/pci/pci-sysfs.c static const struct attribute_group pci_dev_config_attr_group = { · line 926
Quoted 10 lines
drivers/pci/pci-sysfs.c +10
-0+int bar; + +if (attr->size) +return fixed_size_llseek (filep, offset, whence, attr->size); + + pdev =to_pci_dev (kobj_to_dev (kobj)); + bar = (unsigned long )attr->private; + +return fixed_size_llseek (filep, offset, whence, +pci_resource_len (pdev, bar));
Is there a case where using "attr->size" is better than using "pci_resource_len(pdev, bar)"?
In other words, would the following be equivalent?
pci_llseek_resource(...)
{
...
pdev = to_pci_dev(kobj_to_dev(kobj));
bar = (unsigned long)attr->private; return fixed_size_llseek(filep, offset, whence,
pci_resource_len(pdev, bar));
}
Re: [PATCH v6 04/24] PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
Hello,
Quoted 33 lines
Quoted 11 lines
drivers/pci/pci-sysfs.c +2
-2@@ -909,11 +909,21 @@ static const struct attribute_group pci_dev_config_attr_group = {*/ static __maybe_unused loff_t pci_llseek_resource (struct file *filep, -struct kobject *kobj__always_unused , +struct kobject *kobj,const struct bin_attribute *attr,loff_t offset,int whence) { -return fixed_size_llseek (filep, offset, whence, attr->size); +struct pci_dev *pdev;drivers/pci/pci-sysfs.c static const struct attribute_group pci_dev_config_attr_group = { · line 926
Quoted 10 lines
drivers/pci/pci-sysfs.c +10
-0+int bar; + +if (attr->size) +return fixed_size_llseek (filep, offset, whence, attr->size); + + pdev =to_pci_dev (kobj_to_dev (kobj)); + bar = (unsigned long )attr->private; + +return fixed_size_llseek (filep, offset, whence, +pci_resource_len (pdev, bar));Is there a case where using "
attr->size" is better than using "pci_resource_len(pdev, bar)"?In other words, would the following be equivalent?
pci_llseek_resource(...) { ... pdev = to_pci_dev(kobj_to_dev(kobj)); bar = (unsigned long)attr->private;
Quoted 3 lines
return fixed_size_llseek(filep, offset, whence,
pci_resource_len(pdev, bar));
}
Sadly, the simplified version would break legacy attributes.
pci_llseek_resource() is shared between device-level resource attributes and bus-level legacy attributes, both have different semantics:
- Resource attributes (resource0, resource0_wc, ...) are per-device, carry a BAR index in attr->private, and will have .size == 0 with the static conversion.
- Legacy attributes (legacy_io, legacy_mem, ...) are per-bus, have no BAR index in attr->private, and carry a fixed .size (PCI_LEGACY_IO_SIZE, PCI_LEGACY_MEM_SIZE, etc.).
The if (attr->size) check distinguishes the two cases, where legacy attributes have size set at compile time (no BAR index), and the resource attributes derive it from the BAR at runtime.
For legacy attributes, the kobj belongs to a struct pci_bus, not a struct pci_dev, so to_pci_dev(kobj_to_dev(kobj)) would be a wrong type for container_of(). Also, the pci_resource_len() helper would not work there either.
Thus, dropping the attr->size check and always using pci_resource_len() would break the legacy attributes case.
The alternative would be separate llseek callbacks for both the legacy and resource attributes, which we can add if this would be the preference here.
I hope this clears this up a little bit.
Thank you!
Krzysztof
Re: [PATCH v6 04/24] PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
Hello,
Quoted 3 lines
The alternative would be separate llseek callbacks for both the legacy and resource attributes, which we can add if this would be the preference here.
If we were to do this, then it would be as follows:
static loff_t pci_llseek_resource(struct file *filep,
struct kobject *kobj,
const struct bin_attribute *attr,
loff_t offset, int whence)
{
struct pci_dev *pdev = to_pci_dev(kobj_to_dev(kobj));
int bar = (unsigned long)attr->private; return fixed_size_llseek(filep, offset, whence,
pci_resource_len(pdev, bar));
}
static loff_t pci_llseek_resource_legacy(struct file *filep,
struct kobject *kobj __always_unused, const struct bin_attribute *attr, loff_t offset, int whence)
{
return fixed_size_llseek(filep, offset, whence, attr->size);}
Each callback would be placed within the corresponding #ifdef block, so one for HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE, and the other for the legacy attributes, so behind the HAVE_PCI_LEGACY guard.
Note, the names need to be different, as some architectures offer both type of resource files, like PowerPC, which defines both the HAVE_PCI_LEGACY and HAVE_PCI_MMAP.
With this split, we can also drop the __maybe_unused annotation.
While I wanted to keep the changes to only what was needed for the pci_llseek_resource() to cover both type of resources, it would be also fine to have two distinct callbacks, too.
Thank you!
Krzysztof
Re: [PATCH v6 04/24] PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
Quoted 36 lines · Krzysztof Wilczyński
Hello,
Quoted 3 lines
The alternative would be separate llseek callbacks for both the legacy and resource attributes, which we can add if this would be the preference here.
If we were to do this, then it would be as follows:
static loff_t pci_llseek_resource(struct file *filep, struct kobject *kobj, const struct bin_attribute *attr, loff_t offset, int whence) { struct pci_dev *pdev = to_pci_dev(kobj_to_dev(kobj)); int bar = (unsigned long)attr->private;return fixed_size_llseek(filep, offset, whence,
pci_resource_len(pdev, bar));
}static
loff_tpci_llseek_resource_legacy(struct file *filep,
struct kobject *kobj__always_unused, const structbin_attribute*attr,loff_toffset, int whence){ return fixed_size_llseek(filep, offset, whence, attr->size);}
Each callback would be placed within the corresponding #ifdef block, so one for
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE, and the other for the legacy attributes, so behind theHAVE_PCI_LEGACYguard.Note, the names need to be different, as some architectures offer both type of resource files, like PowerPC, which defines both the
HAVE_PCI_LEGACYandHAVE_PCI_MMAP.
Quoted 5 lines
With this split, we can also drop the
__maybe_unusedannotation.While I wanted to keep the changes to only what was needed for the
pci_llseek_resource()to cover both type of resources, it would be also fine to have two distinct callbacks, too.
Yes, I think this is much more readable than the "if (attr->size)" check.
Re: [PATCH v6 04/24] PCI/sysfs: Use BAR length in pci_llseek_resource() when attr->size is zero
Hello,
Quoted 34 lines
Quoted 34 lines
Quoted 3 lines
The alternative would be separate llseek callbacks for both the legacy and resource attributes, which we can add if this would be the preference here.
If we were to do this, then it would be as follows:
static loff_t pci_llseek_resource(struct file *filep, struct kobject *kobj, const struct bin_attribute *attr, loff_t offset, int whence) { struct pci_dev *pdev = to_pci_dev(kobj_to_dev(kobj)); int bar = (unsigned long)attr->private;return fixed_size_llseek(filep, offset, whence,
pci_resource_len(pdev, bar));
}static
loff_tpci_llseek_resource_legacy(struct file *filep,
struct kobject *kobj__always_unused,
const structbin_attribute*attr,loff_toffset, int whence){ return fixed_size_llseek(filep, offset, whence, attr->size);}
Each callback would be placed within the corresponding #ifdef block, so one for
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE, and the other for the legacy attributes, so behind theHAVE_PCI_LEGACYguard.Note, the names need to be different, as some architectures offer both type of resource files, like PowerPC, which defines both the
HAVE_PCI_LEGACYandHAVE_PCI_MMAP.
Quoted 8 lines
Quoted 5 lines
With this split, we can also drop the
__maybe_unusedannotation.While I wanted to keep the changes to only what was needed for the
pci_llseek_resource()to cover both type of resources, it would be also fine to have two distinct callbacks, too.Yes, I think this is much more readable than the "if (
attr->size)" check.
OK. I will switch to two llseek callbacks in the next version.
Thank you,
Krzysztof
PATCH v6 5/24 PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store()
In reply to Krzysztof WilczyńskiCurrently, the __resource_resize_store() allows writing to the resourceN_resize sysfs attribute to change a BAR's size without checking for capabilities, currently relying only on the file access check.
Resizing a BAR modifies PCI device configuration and can disrupt active drivers. After the upcoming conversion to static attributes, it will also trigger resource file updates via sysfs_update_groups().
Thus, add a CAP_SYS_ADMIN check to prevent unprivileged users from performing BAR resize operations.
--- drivers/pci/pci-sysfs.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/pci/pci-sysfs.c +3 -0
@@ -1619,6 +1619,9 @@ static ssize_t __resource_resize_store(struct device *dev, int n,int ret;u16 cmd; +if (!capable (CAP_SYS_ADMIN )) +return -EPERM ; +if (kstrtoul (buf,0 , &size) <0 )return -EINVAL ;
Signature · 1 line
2.54.0
PATCH v6 6/24 PCI/sysfs: Add static PCI resource attribute macros
In reply to Krzysztof WilczyńskiAdd three macros for declaring static binary attributes for PCI resource files:
- pci_dev_resource_io_attr(), for I/O BAR resources (read/write)
- pci_dev_resource_uc_attr(), for memory BAR resources (mmap uncached)
- pci_dev_resource_wc_attr(), for write-combine resources (mmap WC)
Each macro only sets the callbacks its resource type needs. The I/O macro conditionally includes mmap support via __PCI_RESOURCE_IO_MMAP_ATTRS on architectures where arch_can_pci_mmap_io() is true at compile time (such as PowerPC, SPARC, and Xtensa).
--- drivers/pci/pci-sysfs.c | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+)
drivers/pci/pci-sysfs.c +41 -0
@@ -1220,6 +1220,47 @@ static ssize_t pci_write_resource_io(struct file *filp, struct kobject *kobj,return pci_resource_io (filp, kobj, attr, buf, off, count, true); } +/* +* generic_file_llseek() consults f_mapping->host to determine +* the file size. As iomem_inode knows nothing about the +* attribute, it's not going to work, so override it as well. +*/ +#if arch_can_pci_mmap_io () +# define __PCI_RESOURCE_IO_MMAP_ATTRS \ + .f_mapping = iomem_get_mapping, \ + .llseek = pci_llseek_resource, \ + .mmap = pci_mmap_resource_uc, +#else +# define __PCI_RESOURCE_IO_MMAP_ATTRS +#endif + +#define pci_dev_resource_io_attr (_bar) \ +static const struct bin_attribute dev_resource##_bar##_io_attr = { \ + .attr = { .name = "resource" __stringify(_bar), .mode = 0600 }, \ + .private = (void *)(unsigned long)(_bar), \ + .read = pci_read_resource_io, \ + .write = pci_write_resource_io, \ + __PCI_RESOURCE_IO_MMAP_ATTRS \ +} + +#define pci_dev_resource_uc_attr (_bar) \ +static const struct bin_attribute dev_resource##_bar##_uc_attr = { \ + .attr = { .name = "resource" __stringify(_bar), .mode = 0600 }, \ + .private = (void *)(unsigned long)(_bar), \ + .f_mapping = iomem_get_mapping, \ + .llseek = pci_llseek_resource, \ + .mmap = pci_mmap_resource_uc, \ +} + +#define pci_dev_resource_wc_attr (_bar) \ +static const struct bin_attribute dev_resource##_bar##_wc_attr = { \ + .attr = { .name = "resource" __stringify(_bar) "_wc", .mode = 0600 }, \ + .private = (void *)(unsigned long)(_bar), \ + .f_mapping = iomem_get_mapping, \ + .llseek = pci_llseek_resource, \ + .mmap = pci_mmap_resource_wc, \ +} +/** * pci_remove_resource_files - cleanup resource files * @pdev: dev to cleanup
Signature · 1 line
2.54.0
PATCH v6 7/24 PCI/sysfs: Convert PCI resource files to static attributes
In reply to Krzysztof WilczyńskiCurrently, the PCI resource files (resourceN, resourceN_wc) are dynamically created by pci_create_sysfs_dev_files(), called from both pci_bus_add_device() and the pci_sysfs_init() late_initcall, with only a sysfs_initialized flag for synchronisation. This has caused "duplicate filename" warnings and boot panics when both paths race on the same device.
This is especially likely on Devicetree-based platforms, where the PCI host controllers are platform drivers that probe via the driver model, which can happen during or after the late_initcall. As such, pci_bus_add_device() and pci_sysfs_init() are more likely to overlap.
Thus, convert to static const attributes with three attribute groups (I/O, UC, WC), each with an .is_bin_visible callback that checks resource flags, BAR length, and non_mappable_bars. A .bin_size callback provides pci_resource_len() to the kernfs node for correct stat and lseek behaviour.
As part of this conversion:
- Rename pci_read_resource_io() and pci_write_resource_io() to pci_read_resource() and pci_write_resource() since the callbacks are no longer I/O-specific in the static attribute context.
- Update __resource_resize_store() to use sysfs_create_groups() and sysfs_remove_groups(), which re-evaluates visibility and runs the .bin_size callback for the static resource attribute groups.
- Remove pci_create_resource_files(), pci_remove_resource_files(), and pci_create_attr() which are no longer needed.
- Move the __weak stubs outside the #if guard so they remain available for callers converted in subsequent commits.
Platforms that do not define the HAVE_PCI_MMAP macro or the ARCH_GENERIC_PCI_MMAP_RESOURCE macro, such as Alpha architecture, continue using their platform-specific resource file creation.
For reference, the dynamic creation dates back to the pre-Git era:
The write-combine support was added in commit 45aec1ae72fc ("x86: PAT export resource_wc in pci sysfs").
--- drivers/pci/pci-sysfs.c | 260 +++++++++++++++++++++------------------- include/linux/pci.h | 2 - 2 files changed, 140 insertions(+), 122 deletions(-)
drivers/pci/pci-sysfs.c +140 -120
@@ -1200,14 +1200,14 @@ static ssize_t pci_resource_io(struct file *filp, struct kobject *kobj,#endif } -static ssize_t pci_read_resource_io (struct file *filp,struct kobject *kobj, +static ssize_t pci_read_resource (struct file *filp,struct kobject *kobj,const struct bin_attribute *attr,char *buf,loff_t off,size_t count) {return pci_resource_io (filp, kobj, attr, buf, off, count, false); } -static ssize_t pci_write_resource_io (struct file *filp,struct kobject *kobj, +static ssize_t pci_write_resource (struct file *filp,struct kobject *kobj,const struct bin_attribute *attr,char *buf,loff_t off,size_t count) {
@@ -1238,8 +1238,8 @@ static ssize_t pci_write_resource_io(struct file *filp, struct kobject *kobj, static const struct bin_attribute dev_resource##_bar##_io_attr = { \ .attr = { .name ="resource" __stringify(_bar), .mode =0600 }, \ .private = (void *)(unsigned long )(_bar), \ - .read = pci_read_resource_io, \ - .write = pci_write_resource_io, \ + .read = pci_read_resource, \ + .write = pci_write_resource, \ __PCI_RESOURCE_IO_MMAP_ATTRS \ }
@@ -1261,129 +1261,144 @@ static const struct bin_attribute dev_resource##_bar##_wc_attr = { \ .mmap = pci_mmap_resource_wc, \ } -/** -* pci_remove_resource_files - cleanup resource files -* @pdev: dev to cleanup -* -* If we created resource files for @pdev, remove them from sysfs and -* free their resources. -*/ -static void pci_remove_resource_files (struct pci_dev *pdev) +static inline umode_t +__pci_resource_attr_is_visible (struct kobject *kobj, +const struct bin_attribute *a, +int bar,bool write_combine, +unsigned long flags) { -int i; +struct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj)); -for (i =0 ; i <PCI_STD_NUM_BARS ; i++) { -struct bin_attribute *res_attr; - - res_attr = pdev->res_attr[i]; -if (res_attr) { -sysfs_remove_bin_file (&pdev->dev.kobj, res_attr); -kfree (res_attr); - } - - res_attr = pdev->res_attr_wc[i]; -if (res_attr) { -sysfs_remove_bin_file (&pdev->dev.kobj, res_attr); -kfree (res_attr); - } - } -} - -static int pci_create_attr (struct pci_dev *pdev,int num,int write_combine) -{ -/* allocate attribute structure, piggyback attribute name */ -int name_len = write_combine ?13 :10 ; -struct bin_attribute *res_attr; -char *res_attr_name; -int retval; - - res_attr =kzalloc (sizeof (*res_attr) + name_len,GFP_ATOMIC ); -if (!res_attr) -return -ENOMEM ; - - res_attr_name = (char *)(res_attr +1 ); - -sysfs_bin_attr_init (res_attr); -if (write_combine) { -sprintf (res_attr_name,"resource%d_wc" , num); - res_attr->mmap = pci_mmap_resource_wc; - }else { -sprintf (res_attr_name,"resource%d" , num); -if (pci_resource_flags (pdev, num) &IORESOURCE_IO ) { - res_attr->read = pci_read_resource_io; - res_attr->write = pci_write_resource_io; -if (arch_can_pci_mmap_io ()) - res_attr->mmap = pci_mmap_resource_uc; - }else { - res_attr->mmap = pci_mmap_resource_uc; - } - } -if (res_attr->mmap) { - res_attr->f_mapping = iomem_get_mapping; -/* -* generic_file_llseek() consults f_mapping->host to determine -* the file size. As iomem_inode knows nothing about the -* attribute, it's not going to work, so override it as well. -*/ - res_attr->llseek = pci_llseek_resource; - } - res_attr->attr.name = res_attr_name; - res_attr->attr.mode =0600 ; - res_attr->size =pci_resource_len (pdev, num); - res_attr->private = (void *)(unsigned long )num; - retval =sysfs_create_bin_file (&pdev->dev.kobj, res_attr); -if (retval) { -kfree (res_attr); -return retval; - } - -if (write_combine) - pdev->res_attr_wc[num] = res_attr; -else - pdev->res_attr[num] = res_attr; - -return 0 ; -} - -/** -* pci_create_resource_files - create resource files in sysfs for @dev -* @pdev: dev in question -* -* Walk the resources in @pdev creating files for each resource available. -*/ -static int pci_create_resource_files (struct pci_dev *pdev) -{ -int i; -int retval; - -/* Skip devices with non-mappable BARs */ if (pdev->non_mappable_bars)return 0 ; -/* Expose the PCI resources from this device as files */ -for (i =0 ; i <PCI_STD_NUM_BARS ; i++) { +if (!pci_resource_len (pdev, bar)) +return 0 ; -/* skip empty resources */ -if (!pci_resource_len (pdev, i)) -continue ; +if ((pci_resource_flags (pdev, bar) & flags) != flags) +return 0 ; - retval =pci_create_attr (pdev, i,0 ); -/* for prefetchable resources, create a WC mappable file */ -if (!retval &&arch_can_pci_mmap_wc () && -pci_resource_flags (pdev, i) &IORESOURCE_PREFETCH ) - retval =pci_create_attr (pdev, i,1 ); -if (retval) { -pci_remove_resource_files (pdev); -return retval; - } - } -return 0 ; +if (write_combine && !arch_can_pci_mmap_wc ()) +return 0 ; + +return a->attr.mode; } -#else /* !(defined(HAVE_PCI_MMAP) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE)) */ -int __weak pci_create_resource_files (struct pci_dev *dev) {return 0 ; } -void __weak pci_remove_resource_files (struct pci_dev *dev) {return ; } + +static umode_t pci_dev_resource_io_is_visible (struct kobject *kobj, +const struct bin_attribute *a, +int n) +{ +return __pci_resource_attr_is_visible (kobj, a, n, false, +IORESOURCE_IO ); +} + +static umode_t pci_dev_resource_uc_is_visible (struct kobject *kobj, +const struct bin_attribute *a, +int n) +{ +return __pci_resource_attr_is_visible (kobj, a, n, false, +IORESOURCE_MEM ); +} + +static umode_t pci_dev_resource_wc_is_visible (struct kobject *kobj, +const struct bin_attribute *a, +int n) +{ +return __pci_resource_attr_is_visible (kobj, a, n, true, +IORESOURCE_MEM |IORESOURCE_PREFETCH ); +} + +static size_t pci_dev_resource_bin_size (struct kobject *kobj, +const struct bin_attribute *a, +int n) +{ +struct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj)); + +return pci_resource_len (pdev, n); +} + +pci_dev_resource_io_attr (0 ); +pci_dev_resource_io_attr (1 ); +pci_dev_resource_io_attr (2 ); +pci_dev_resource_io_attr (3 ); +pci_dev_resource_io_attr (4 ); +pci_dev_resource_io_attr (5 ); + +pci_dev_resource_uc_attr (0 ); +pci_dev_resource_uc_attr (1 ); +pci_dev_resource_uc_attr (2 ); +pci_dev_resource_uc_attr (3 ); +pci_dev_resource_uc_attr (4 ); +pci_dev_resource_uc_attr (5 ); + +pci_dev_resource_wc_attr (0 ); +pci_dev_resource_wc_attr (1 ); +pci_dev_resource_wc_attr (2 ); +pci_dev_resource_wc_attr (3 ); +pci_dev_resource_wc_attr (4 ); +pci_dev_resource_wc_attr (5 ); + +static const struct bin_attribute *const pci_dev_resource_io_attrs[] = { + &dev_resource0_io_attr, + &dev_resource1_io_attr, + &dev_resource2_io_attr, + &dev_resource3_io_attr, + &dev_resource4_io_attr, + &dev_resource5_io_attr, +NULL , +}; + +static const struct bin_attribute *const pci_dev_resource_uc_attrs[] = { + &dev_resource0_uc_attr, + &dev_resource1_uc_attr, + &dev_resource2_uc_attr, + &dev_resource3_uc_attr, + &dev_resource4_uc_attr, + &dev_resource5_uc_attr, +NULL , +}; + +static const struct bin_attribute *const pci_dev_resource_wc_attrs[] = { + &dev_resource0_wc_attr, + &dev_resource1_wc_attr, + &dev_resource2_wc_attr, + &dev_resource3_wc_attr, + &dev_resource4_wc_attr, + &dev_resource5_wc_attr, +NULL , +}; + +static const struct attribute_group pci_dev_resource_io_attr_group = { + .bin_attrs = pci_dev_resource_io_attrs, + .is_bin_visible = pci_dev_resource_io_is_visible, + .bin_size = pci_dev_resource_bin_size, +}; + +static const struct attribute_group pci_dev_resource_uc_attr_group = { + .bin_attrs = pci_dev_resource_uc_attrs, + .is_bin_visible = pci_dev_resource_uc_is_visible, + .bin_size = pci_dev_resource_bin_size, +}; + +static const struct attribute_group pci_dev_resource_wc_attr_group = { + .bin_attrs = pci_dev_resource_wc_attrs, + .is_bin_visible = pci_dev_resource_wc_is_visible, + .bin_size = pci_dev_resource_bin_size, +}; + +static const struct attribute_group *pci_dev_resource_attr_groups[] = { + &pci_dev_resource_io_attr_group, + &pci_dev_resource_uc_attr_group, + &pci_dev_resource_wc_attr_group, +NULL , +}; +#else +#define pci_dev_resource_attr_groups NULL#endif +int __weak pci_create_resource_files (struct pci_dev *dev) {return 0 ; } +void __weak pci_remove_resource_files (struct pci_dev *dev) { } +/** * pci_write_rom - used to enable access to the PCI ROM display * @filp: sysfs file
@@ -1685,14 +1700,14 @@ static ssize_t __resource_resize_store(struct device *dev, int n,pci_write_config_word (pdev,PCI_COMMAND , cmd & ~PCI_COMMAND_MEMORY ); -pci_remove_resource_files (pdev); +sysfs_remove_groups (&pdev->dev.kobj, pci_dev_resource_attr_groups); ret =pci_resize_resource (pdev, n, size,0 );pci_assign_unassigned_bus_resources (bus); -if (pci_create_resource_files (pdev)) -pci_warn (pdev,"Failed to recreate resource files after BAR resizing\n" ); +if (sysfs_create_groups (&pdev->dev.kobj, pci_dev_resource_attr_groups)) +pci_warn (pdev,"Failed to recreate resource groups after BAR resizing\n" );pci_write_config_word (pdev,PCI_COMMAND , cmd); pm_put:
@@ -1861,6 +1876,11 @@ static const struct attribute_group pci_dev_group = {const struct attribute_group *pci_dev_groups[] = { &pci_dev_group, +#if defined(HAVE_PCI_MMAP) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE) + &pci_dev_resource_io_attr_group, + &pci_dev_resource_uc_attr_group, + &pci_dev_resource_wc_attr_group, +#endif &pci_dev_config_attr_group, &pci_dev_rom_attr_group, &pci_dev_reset_attr_group,
include/linux/pci.h +0 -2
@@ -2526,10 +2526,8 @@ int pcibios_alloc_irq(struct pci_dev *dev);void pcibios_free_irq (struct pci_dev *dev);resource_size_t pcibios_default_alignment (void ); -#if !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )extern int pci_create_resource_files (struct pci_dev *dev);extern void pci_remove_resource_files (struct pci_dev *dev); -#endif #if defined(CONFIG_PCI_MMCONFIG ) || defined(CONFIG_ACPI_MCFG )void __init pci_mmcfg_early_init (void );
Signature · 1 line
2.54.0
PATCH v6 8/24 PCI/sysfs: Warn about BAR resize failure in __resource_resize_store()
In reply to Krzysztof WilczyńskiAdd a pci_warn() to __resource_resize_store(), so that BAR resize failures are visible to the user, which can help troubleshoot any potential resource resize issues.
While at it, rename the resource_resize_is_visible() to resource_resize_attr_is_visible() along with the corresponding group variable to align with the naming convention used by the resource attribute groups.
Also, change the order of pci_dev_groups[] such that the resize group is now located alongside the other resource groups.
--- drivers/pci/pci-sysfs.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/pci/pci-sysfs.c +7 -4
@@ -1703,6 +1703,9 @@ static ssize_t __resource_resize_store(struct device *dev, int n,sysfs_remove_groups (&pdev->dev.kobj, pci_dev_resource_attr_groups); ret =pci_resize_resource (pdev, n, size,0 ); +if (ret) +pci_warn (pdev,"Failed to resize BAR %d: %pe\n" , + n,ERR_PTR (ret));pci_assign_unassigned_bus_resources (bus);
@@ -1750,7 +1753,7 @@ static struct attribute *resource_resize_attrs[] = { NULL, }; -static umode_t resource_resize_is_visible (struct kobject *kobj, +static umode_t resource_resize_attr_is_visible (struct kobject *kobj,struct attribute *a,int n) {struct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj));
@@ -1758,9 +1761,9 @@ static umode_t resource_resize_is_visible(struct kobject *kobj,return pci_rebar_get_current_size (pdev, n) <0 ?0 : a->mode; } -static const struct attribute_group pci_dev_resource_resize_group = { +static const struct attribute_group pci_dev_resource_resize_attr_group = { .attrs = resource_resize_attrs, - .is_visible = resource_resize_is_visible, + .is_visible = resource_resize_attr_is_visible, };int __must_check pci_create_sysfs_dev_files (struct pci_dev *pdev)
@@ -1881,6 +1884,7 @@ const struct attribute_group *pci_dev_groups[] = { &pci_dev_resource_uc_attr_group, &pci_dev_resource_wc_attr_group, #endif + &pci_dev_resource_resize_attr_group, &pci_dev_config_attr_group, &pci_dev_rom_attr_group, &pci_dev_reset_attr_group,
@@ -1892,7 +1896,6 @@ const struct attribute_group *pci_dev_groups[] = {#ifdef CONFIG_ACPI &pci_dev_acpi_attr_group,#endif - &pci_dev_resource_resize_group, ARCH_PCI_DEV_GROUPS NULL, };
Signature · 1 line
2.54.0
PATCH v6 9/24 PCI/sysfs: Add stubs for pci_{create,remove}_sysfs_dev_files()
In reply to Krzysztof WilczyńskiOn platforms with HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE, resource files are now handled by static attribute groups registered via pci_dev_groups[].
Thus, the pci_create_sysfs_dev_files() and pci_remove_sysfs_dev_files() can now be stubbed out, as the dynamic resource file creation is no longer needed.
Also, simplify pci_sysfs_init() on these platforms to only iterate buses for legacy attributes creation, skipping the per-device loop.
Move the __weak stubs for pci_create_resource_files() and pci_remove_resource_files() into the #else branch since only platforms without HAVE_PCI_MMAP (such as Alpha architecture) still need them. Guard the res_attr[] and res_attr_wc[] fields in struct pci_dev the same way.
--- drivers/pci/pci-sysfs.c | 15 ++++++++++++--- include/linux/pci.h | 4 ++++ 2 files changed, 16 insertions(+), 3 deletions(-)
drivers/pci/pci-sysfs.c +12 -3
@@ -1394,10 +1394,9 @@ static const struct attribute_group *pci_dev_resource_attr_groups[] = { };#else #define pci_dev_resource_attr_groups NULL -#endif -int __weak pci_create_resource_files (struct pci_dev *dev) {return 0 ; }void __weak pci_remove_resource_files (struct pci_dev *dev) { } +#endif /** * pci_write_rom - used to enable access to the PCI ROM display
@@ -1766,6 +1765,10 @@ static const struct attribute_group pci_dev_resource_resize_attr_group = { .is_visible = resource_resize_attr_is_visible, }; +#if defined(HAVE_PCI_MMAP ) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE ) +int pci_create_sysfs_dev_files (struct pci_dev *pdev) {return 0 ; } +void pci_remove_sysfs_dev_files (struct pci_dev *pdev) { } +#else int __must_check pci_create_sysfs_dev_files (struct pci_dev *pdev) {if (!sysfs_initialized)
@@ -1787,9 +1790,15 @@ void pci_remove_sysfs_dev_files(struct pci_dev *pdev) pci_remove_resource_files(pdev); } +#endif static int __init pci_sysfs_init (void ) { +#if defined(HAVE_PCI_MMAP ) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE ) +struct pci_bus *pbus =NULL ; + + sysfs_initialized =1 ; +#else struct pci_dev *pdev =NULL ;struct pci_bus *pbus =NULL ;int retval;
@@ -1802,7 +1811,7 @@ static int __init pci_sysfs_init(void) return retval; } } - +#endif while ((pbus =pci_find_next_bus (pbus)))pci_create_legacy_files (pbus);
include/linux/pci.h +4 -0
@@ -507,8 +507,10 @@ struct pci_dev {spinlock_t pcie_cap_lock;/* Protects RMW ops in capability accessors */ u32 saved_config_space[16 ];/* Config space saved at suspend time */ struct hlist_head saved_cap_space; +#if !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )struct bin_attribute *res_attr[DEVICE_COUNT_RESOURCE ];/* sysfs file for resources */ struct bin_attribute *res_attr_wc[DEVICE_COUNT_RESOURCE ];/* sysfs file for WC mapping of resources */ +#endif #ifdef CONFIG_HOTPLUG_PCI_PCIE unsigned int broken_cmd_compl:1; /* No compl for some cmds */
@@ -2526,8 +2528,10 @@ int pcibios_alloc_irq(struct pci_dev *dev);void pcibios_free_irq (struct pci_dev *dev);resource_size_t pcibios_default_alignment (void ); +#if !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )extern int pci_create_resource_files (struct pci_dev *dev);extern void pci_remove_resource_files (struct pci_dev *dev); +#endif #if defined(CONFIG_PCI_MMCONFIG ) || defined(CONFIG_ACPI_MCFG )void __init pci_mmcfg_early_init (void );
Signature · 1 line
2.54.0
PATCH v6 10/24 PCI/sysfs: Limit pci_sysfs_init() late_initcall compile scope
In reply to Krzysztof WilczyńskiCurrently, pci_sysfs_init() and sysfs_initialized compile unconditionally, even on platforms where static attribute groups handle all resource file creation.
Thus, place them behind a new HAVE_PCI_SYSFS_INIT macro, especially as the late_initcall is only needed when:
- HAVE_PCI_LEGACY is set, to iterate buses and create legacy I/O and memory files.
- Neither HAVE_PCI_MMAP nor ARCH_GENERIC_PCI_MMAP_RESOURCE is set, to iterate devices and create resource files via the __weak pci_create_resource_files() stub override (this is how the Alpha architecture handles this currently).
On most systems both conditions are false and the entire late_initcall compiles away.
--- drivers/pci/pci-sysfs.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/pci/pci-sysfs.c +9 -0
@@ -37,7 +37,14 @@#define ARCH_PCI_DEV_GROUPS #endif +#if defined(HAVE_PCI_LEGACY ) || \ + !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE ) +#define HAVE_PCI_SYSFS_INIT +#endif + +#ifdef HAVE_PCI_SYSFS_INIT static int sysfs_initialized;/* = 0 */ +#endif /* show configuration fields */ #define pci_config_attr (field, format_string) \
@@ -1792,6 +1799,7 @@ void pci_remove_sysfs_dev_files(struct pci_dev *pdev) }#endif +#ifdef HAVE_PCI_SYSFS_INIT static int __init pci_sysfs_init (void ) {#if defined(HAVE_PCI_MMAP ) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )
@@ -1818,6 +1826,7 @@ static int __init pci_sysfs_init(void)return 0 ; }late_initcall (pci_sysfs_init); +#endif static struct attribute *pci_dev_dev_attrs[] = { &dev_attr_boot_vga.attr,
Signature · 1 line
2.54.0
PATCH v6 11/24 alpha/PCI: Add security_locked_down() check to pci_mmap_resource()
In reply to Krzysztof WilczyńskiCurrently, Alpha's pci_mmap_resource() does not check security_locked_down(LOCKDOWN_PCI_ACCESS) before allowing userspace to mmap PCI BARs.
The generic version has had this check since commit eb627e17727e ("PCI: Lock down BAR access when the kernel is locked down") to prevent DMA attacks when the kernel is locked down.
Add the same check to Alpha's pci_mmap_resource().
--- arch/alpha/kernel/pci-sysfs.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
arch/alpha/kernel/pci-sysfs.c +6 -1
@@ -11,6 +11,7 @@*/ #include <linux/sched.h> +#include <linux/security.h> #include <linux/stat.h> #include <linux/slab.h> #include <linux/pci.h>
@@ -71,7 +72,11 @@ static int pci_mmap_resource(struct kobject *kobj,struct resource *res = attr->private;enum pci_mmap_state mmap_type;struct pci_bus_region bar; -int i; +int i, ret; + + ret =security_locked_down (LOCKDOWN_PCI_ACCESS ); +if (ret) +return ret;for (i =0 ; i <PCI_STD_NUM_BARS ; i++)if (res == &pdev->resource[i])
Signature · 1 line
2.54.0
PATCH v6 12/24 alpha/PCI: Use BAR index in sysfs attr->private instead of resource pointer
In reply to Krzysztof WilczyńskiCurrently, Alpha's pci_create_one_attr() stores a resource pointer in attr->private, and pci_mmap_resource() loops through all BARs to find the matching index.
Thus, store the BAR index directly in attr->private and retrieve the resource via pci_resource_n(). This eliminates the loop and aligns with the convention used by the generic PCI sysfs code.
The PCI core change was first added in the commit dca40b186b75 ("PCI:
Use BAR index in sysfs attr->private instead of resource pointer").
--- arch/alpha/kernel/pci-sysfs.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-)
arch/alpha/kernel/pci-sysfs.c +5 -10
@@ -69,25 +69,20 @@ static int pci_mmap_resource(struct kobject *kobj, struct vm_area_struct *vma, int sparse) {struct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj)); -struct resource *res = attr->private; +int barno = (unsigned long )attr->private; +struct resource *res =pci_resource_n (pdev, barno);enum pci_mmap_state mmap_type;struct pci_bus_region bar; -int i, ret; +int ret; ret =security_locked_down (LOCKDOWN_PCI_ACCESS );if (ret)return ret; -for (i =0 ; i <PCI_STD_NUM_BARS ; i++) -if (res == &pdev->resource[i]) -break ; -if (i >=PCI_STD_NUM_BARS ) -return -ENODEV ; -if (res->flags &IORESOURCE_MEM &&iomem_is_exclusive (res->start))return -EINVAL ; -if (!__pci_mmap_fits (pdev, i, vma, sparse)) +if (!__pci_mmap_fits (pdev, barno, vma, sparse))return -EINVAL ;pcibios_resource_to_bus (pdev->bus, &bar, res);
@@ -170,7 +165,7 @@ static int pci_create_one_attr(struct pci_dev *pdev, int num, char *name, res_attr->attr.name = name; res_attr->attr.mode =S_IRUSR |S_IWUSR ; res_attr->size = sparse ? size <<5 : size; - res_attr->private = &pdev->resource[num]; + res_attr->private = (void *)(unsigned long )num;return sysfs_create_bin_file (&pdev->dev.kobj, res_attr); }
Signature · 1 line
2.54.0
PATCH v6 13/24 alpha/PCI: Use PCI resource accessor macros
In reply to Krzysztof WilczyńskiReplace direct pdev->resource[] accesses with pci_resource_n(), and open-coded res->flags type checks with pci_resource_is_mem() and pci_resource_start() helpers.
While at it, move the pci_resource_n() call directly into pcibios_resource_to_bus() and drop the local struct resource pointer.
No functional changes intended.
--- arch/alpha/kernel/pci-sysfs.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
arch/alpha/kernel/pci-sysfs.c +6 -6
@@ -70,7 +70,6 @@ static int pci_mmap_resource(struct kobject *kobj, {struct pci_dev *pdev =to_pci_dev (kobj_to_dev (kobj));int barno = (unsigned long )attr->private; -struct resource *res =pci_resource_n (pdev, barno);enum pci_mmap_state mmap_type;struct pci_bus_region bar;int ret;
@@ -79,15 +78,16 @@ static int pci_mmap_resource(struct kobject *kobj,if (ret)return ret; -if (res->flags &IORESOURCE_MEM &&iomem_is_exclusive (res->start)) +if (pci_resource_is_mem (pdev, barno) && +iomem_is_exclusive (pci_resource_start (pdev, barno)))return -EINVAL ;if (!__pci_mmap_fits (pdev, barno, vma, sparse))return -EINVAL ; -pcibios_resource_to_bus (pdev->bus, &bar, res); +pcibios_resource_to_bus (pdev->bus, &bar,pci_resource_n (pdev, barno)); vma->vm_pgoff += bar.start >> (PAGE_SHIFT - (sparse ?5 :0 )); - mmap_type = res->flags &IORESOURCE_MEM ? pci_mmap_mem : pci_mmap_io; + mmap_type =pci_resource_is_mem (pdev, barno) ? pci_mmap_mem : pci_mmap_io;return hose_mmap_page_range (pdev->sysdata, vma, mmap_type, sparse); }
@@ -141,7 +141,7 @@ static int sparse_mem_mmap_fits(struct pci_dev *pdev, int num)long dense_offset;unsigned long sparse_size; -pcibios_resource_to_bus (pdev->bus, &bar, &pdev->resource[num]); +pcibios_resource_to_bus (pdev->bus, &bar,pci_resource_n (pdev, num));/* All core logic chips have 4G sparse address space, except CIA which has 16G (see xxx_SPARSE_MEM and xxx_DENSE_MEM
@@ -181,7 +181,7 @@ static int pci_create_attr(struct pci_dev *pdev, int num) suffix ="" ;/* Assume bwx machine, normal resourceN files. */ nlen1 =10 ; -if (pdev->resource[num].flags &IORESOURCE_MEM ) { +if (pci_resource_is_mem (pdev, num)) { sparse_base = hose->sparse_mem_base; dense_base = hose->dense_mem_base;if (sparse_base && !sparse_mem_mmap_fits (pdev, num)) {
Signature · 1 line
2.54.0
PATCH v6 14/24 alpha/PCI: Fix __pci_mmap_fits() overflow for zero-length BARs
In reply to Krzysztof WilczyńskiCurrently, __pci_mmap_fits() computes the BAR size using pci_resource_len() - 1, which wraps to a large value when the BAR length is zero, causing the bounds check to incorrectly succeed.
Thus, add an early return for empty resources.
--- arch/alpha/kernel/pci-sysfs.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/alpha/kernel/pci-sysfs.c +5 -1
@@ -37,12 +37,16 @@ static int hose_mmap_page_range(struct pci_controller *hose,static int __pci_mmap_fits (struct pci_dev *pdev,int num,struct vm_area_struct *vma,int sparse) { +resource_size_t len =pci_resource_len (pdev, num);unsigned long nr, start, size;int shift = sparse ?5 :0 ; +if (!len) +return 0 ; + nr =vma_pages (vma); start = vma->vm_pgoff; - size = ((pci_resource_len (pdev, num) -1 ) >> (PAGE_SHIFT - shift)) +1 ; + size = ((len -1 ) >> (PAGE_SHIFT - shift)) +1 ;if (start < size && size - start >= nr)return 1 ;
Signature · 1 line
2.54.0
PATCH v6 15/24 alpha/PCI: Remove WARN from __pci_mmap_fits()
In reply to Krzysztof WilczyńskiRemove the WARN() that fires when userspace attempts to mmap beyond the BAR bounds. The check still returns 0 to reject the mapping, but the warning is excessive for normal operation.
A similar warning was removed from the PCI core in the commit 3b519e4ea618 ("PCI: fix size checks for mmap() on /proc/bus/pci files").
--- arch/alpha/kernel/pci-sysfs.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)
arch/alpha/kernel/pci-sysfs.c +1 -7
@@ -48,13 +48,7 @@ static int __pci_mmap_fits(struct pci_dev *pdev, int num, start = vma->vm_pgoff; size = ((len -1 ) >> (PAGE_SHIFT - shift)) +1 ; -if (start < size && size - start >= nr) -return 1 ; -WARN (1 ,"process \"%s\" tried to map%s 0x%08lx-0x%08lx on %s BAR %d " -"(size 0x%08lx)\n" , - current->comm, sparse ?" sparse" :"" , start, start + nr, -pci_name (pdev), num, size); -return 0 ; +return start < size && size - start >= nr; }/**
Signature · 1 line
2.54.0
PATCH v6 16/24 alpha/PCI: Add static PCI resource attribute macros
In reply to Krzysztof WilczyńskiAdd macros for declaring static binary attributes for Alpha's PCI resource files:
- pci_dev_resource_attr(), for dense/BWX systems (mmap dense)
- pci_dev_resource_sparse_attr(), for sparse systems (mmap sparse)
- pci_dev_resource_dense_attr(), for dense companion files (mmap dense)
Each macro creates a const bin_attribute with the BAR index stored in the .private property and the appropriate .mmap callback.
--- arch/alpha/kernel/pci-sysfs.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
arch/alpha/kernel/pci-sysfs.c +20 -0
@@ -104,6 +104,26 @@ static int pci_mmap_resource_dense(struct file *filp, struct kobject *kobj,return pci_mmap_resource (kobj, attr, vma,0 ); } +#define __pci_dev_resource_attr (_bar, _name, _suffix, _mmap) \ +static const struct bin_attribute \ +pci_dev_resource##_bar##_suffix##_attr = { \ + .attr = { .name = __stringify(_name), .mode = 0600 }, \ + .private = (void *)(unsigned long)(_bar), \ + .mmap = (_mmap), \ +} + +#define pci_dev_resource_attr (_bar) \ + __pci_dev_resource_attr(_bar, resource##_bar,, \ + pci_mmap_resource_dense) + +#define pci_dev_resource_sparse_attr (_bar) \ + __pci_dev_resource_attr(_bar, resource##_bar##_sparse, _sparse, \ + pci_mmap_resource_sparse) + +#define pci_dev_resource_dense_attr (_bar) \ + __pci_dev_resource_attr(_bar, resource##_bar##_dense, _dense, \ + pci_mmap_resource_dense) +/** * pci_remove_resource_files - cleanup resource files * @pdev: pci_dev to cleanup
Signature · 1 line
2.54.0
PATCH v6 17/24 alpha/PCI: Convert resource files to static attributes
In reply to Krzysztof WilczyńskiCurrently, Alpha's PCI resource files (resourceN, resourceN_sparse, resourceN_dense) are dynamically created by pci_create_resource_files(), which overrides the generic __weak implementation. The current code allocates bin_attributes at runtime and manages them via the res_attr[] and res_attr_wc[] fields in struct pci_dev.
Thus, convert to static const attributes with three attribute groups (plain, sparse, dense), each with an .is_bin_visible callback that checks resource length, has_sparse(), and sparse_mem_mmap_fits(). A .bin_size callback provides the resource size to the kernfs node, with the sparse variant shifting by 5 bits for byte-level addressing.
Register the groups via ARCH_PCI_DEV_GROUPS so the driver model handles creation and removal automatically.
Use the new pci_resource_is_mem() helper for the type check, replacing the open-coded bitwise flag test.
Finally, remove pci_create_resource_files(), pci_remove_resource_files(), pci_create_attr(), and pci_create_one_attr() which are no longer needed.
--- arch/alpha/include/asm/pci.h | 9 ++ arch/alpha/kernel/pci-sysfs.c | 291 +++++++++++++++++++--------------- 2 files changed, 172 insertions(+), 128 deletions(-)
arch/alpha/include/asm/pci.h +9 -0
@@ -88,4 +88,13 @@ extern void pci_adjust_legacy_attr(struct pci_bus *bus, enum pci_mmap_state mmap_type);#define HAVE_PCI_LEGACY 1 +extern const struct attribute_group pci_dev_resource_attr_group; +extern const struct attribute_group pci_dev_resource_sparse_attr_group; +extern const struct attribute_group pci_dev_resource_dense_attr_group; + +#define ARCH_PCI_DEV_GROUPS \ + &pci_dev_resource_attr_group, \ + &pci_dev_resource_sparse_attr_group, \ + &pci_dev_resource_dense_attr_group, +#endif /* __ALPHA_PCI_H */
arch/alpha/kernel/pci-sysfs.c +163 -128
312 lines not on this page · raw message
Signature · 1 line
2.54.0
PATCH v6 18/24 PCI/sysfs: Remove pci_{create,remove}_sysfs_dev_files()
In reply to Krzysztof WilczyńskiCurrently, pci_create_sysfs_dev_files() and pci_remove_sysfs_dev_files() are no-op stubs. With both the generic and Alpha resource files now handled by static attribute groups, no platform needs dynamic per-device sysfs file creation.
Thus, remove both functions, their declarations, and the call sites in pci_bus_add_device() and pci_stop_bus_device().
Remove __weak pci_create_resource_files() and pci_remove_resource_files() stubs and their declarations in pci.h, as no architecture overrides them anymore.
Remove the res_attr[] and res_attr_wc[] fields from struct pci_dev which were used to track dynamically allocated resource attributes.
Finally, simplify pci_sysfs_init() to only handle legacy file creation under HAVE_PCI_LEGACY, removing the per-device loop and the HAVE_PCI_SYSFS_INIT helper added earlier.
--- drivers/pci/bus.c | 1 - drivers/pci/pci-sysfs.c | 52 ++--------------------------------------- drivers/pci/pci.h | 4 ---- drivers/pci/remove.c | 1 - include/linux/pci.h | 9 ------- 5 files changed, 2 insertions(+), 65 deletions(-)
drivers/pci/bus.c +0 -1
@@ -354,7 +354,6 @@ void pci_bus_add_device(struct pci_dev *dev)pci_fixup_device (pci_fixup_final, dev);if (pci_is_bridge (dev))of_pci_make_dev_node (dev); -pci_create_sysfs_dev_files (dev);pci_proc_attach_device (dev);pci_bridge_d3_update (dev);
drivers/pci/pci-sysfs.c +2 -50
76 lines not on this page · raw message
drivers/pci/pci.h +0 -4
@@ -391,16 +391,12 @@ static inline int pci_no_d1d2(struct pci_dev *dev) }#ifdef CONFIG_SYSFS -int pci_create_sysfs_dev_files (struct pci_dev *pdev); -void pci_remove_sysfs_dev_files (struct pci_dev *pdev);extern const struct attribute_group *pci_dev_groups[];extern const struct attribute_group *pci_dev_attr_groups[];extern const struct attribute_group *pcibus_groups[];extern const struct attribute_group *pci_bus_groups[];extern const struct attribute_group pci_doe_sysfs_group;#else -static inline int pci_create_sysfs_dev_files (struct pci_dev *pdev) {return 0 ; } -static inline void pci_remove_sysfs_dev_files (struct pci_dev *pdev) { }#define pci_dev_groups NULL#define pci_dev_attr_groups NULL#define pcibus_groups NULL
drivers/pci/remove.c +0 -1
@@ -26,7 +26,6 @@ static void pci_stop_dev(struct pci_dev *dev)device_release_driver (&dev->dev);pci_proc_detach_device (dev); -pci_remove_sysfs_dev_files (dev);of_pci_remove_node (dev); }
include/linux/pci.h +0 -9
@@ -507,10 +507,6 @@ struct pci_dev {spinlock_t pcie_cap_lock;/* Protects RMW ops in capability accessors */ u32 saved_config_space[16 ];/* Config space saved at suspend time */ struct hlist_head saved_cap_space; -#if !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE ) -struct bin_attribute *res_attr[DEVICE_COUNT_RESOURCE ];/* sysfs file for resources */ -struct bin_attribute *res_attr_wc[DEVICE_COUNT_RESOURCE ];/* sysfs file for WC mapping of resources */ -#endif #ifdef CONFIG_HOTPLUG_PCI_PCIE unsigned int broken_cmd_compl:1; /* No compl for some cmds */
@@ -2528,11 +2524,6 @@ int pcibios_alloc_irq(struct pci_dev *dev);void pcibios_free_irq (struct pci_dev *dev);resource_size_t pcibios_default_alignment (void ); -#if !defined(HAVE_PCI_MMAP ) && !defined(ARCH_GENERIC_PCI_MMAP_RESOURCE ) -extern int pci_create_resource_files (struct pci_dev *dev); -extern void pci_remove_resource_files (struct pci_dev *dev); -#endif -#if defined(CONFIG_PCI_MMCONFIG ) || defined(CONFIG_ACPI_MCFG )void __init pci_mmcfg_early_init (void );void __init pci_mmcfg_late_init (void );
Signature · 1 line
2.54.0
PATCH v6 19/24 PCI: Add macros for legacy I/O and memory address space sizes
In reply to Krzysztof WilczyńskiAdd defines for the standard PCI legacy address space sizes, replacing the raw literals used by the legacy sysfs attributes.
Then, replace open-coded values with the newly added macros.
No functional changes intended.
--- drivers/pci/pci-sysfs.c | 4 ++-- include/linux/pci.h | 5 +++++ 2 files changed, 7 insertions(+), 2 deletions(-)
drivers/pci/pci-sysfs.c +2 -2
@@ -1055,7 +1055,7 @@ void pci_create_legacy_files(struct pci_bus *b)sysfs_bin_attr_init (b->legacy_io); b->legacy_io->attr.name ="legacy_io" ; - b->legacy_io->size =0xffff ; + b->legacy_io->size =PCI_LEGACY_IO_SIZE ; b->legacy_io->attr.mode =0600 ; b->legacy_io->read = pci_read_legacy_io; b->legacy_io->write = pci_write_legacy_io;
@@ -1072,7 +1072,7 @@ void pci_create_legacy_files(struct pci_bus *b) b->legacy_mem = b->legacy_io +1 ;sysfs_bin_attr_init (b->legacy_mem); b->legacy_mem->attr.name ="legacy_mem" ; - b->legacy_mem->size =1024 *1024 ; + b->legacy_mem->size =PCI_LEGACY_MEM_SIZE ; b->legacy_mem->attr.mode =0600 ; b->legacy_mem->mmap = pci_mmap_legacy_mem;/* See pci_create_attr() for motivation */
include/linux/pci.h +5 -0
@@ -27,6 +27,7 @@#include <linux/mod_devicetable.h> #include <linux/types.h> +#include <linux/sizes.h> #include <linux/init.h> #include <linux/ioport.h> #include <linux/list.h>
@@ -1167,6 +1168,10 @@ enum {/* These external functions are only available when PCI support is enabled */ #ifdef CONFIG_PCI +/* PCI legacy I/O port and memory address space sizes. */ +#define PCI_LEGACY_IO_SIZE (SZ_64K - 1) +#define PCI_LEGACY_MEM_SIZE SZ_1M +extern unsigned int pci_flags;static inline void pci_set_flags (int flags) { pci_flags = flags; }
Signature · 1 line
2.54.0
PATCH v6 20/24 alpha/PCI: Compute legacy size in pci_mmap_legacy_page_range()
In reply to Krzysztof WilczyńskiCurrently, pci_mmap_legacy_page_range() reads the legacy resource size from bus->legacy_mem->size or bus->legacy_io->size. This couples the mmap bounds check to the struct pci_bus fields that will be removed when legacy attributes are converted to static definitions.
Compute the size directly using PCI_LEGACY_MEM_SIZE (0x100000) and PCI_LEGACY_IO_SIZE (0xffff) macros, and shift by 5 bits for sparse systems.
--- arch/alpha/kernel/pci-sysfs.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
arch/alpha/kernel/pci-sysfs.c +5 -2
@@ -180,8 +180,11 @@ int pci_mmap_legacy_page_range(struct pci_bus *bus, struct vm_area_struct *vma,int sparse =has_sparse (hose, mmap_type);unsigned long res_size; - res_size = (mmap_type == pci_mmap_mem) ? bus->legacy_mem->size : - bus->legacy_io->size; + res_size = (mmap_type == pci_mmap_mem) ?PCI_LEGACY_MEM_SIZE : +PCI_LEGACY_IO_SIZE ; +if (sparse) + res_size <<=5 ; +if (!__legacy_mmap_fits (hose, vma, res_size, sparse))return -EINVAL ;
Signature · 1 line
2.54.0
PATCH v6 21/24 PCI/sysfs: Add __weak pci_legacy_has_sparse() helper
In reply to Krzysztof WilczyńskiCurrently, Alpha's sparse/dense legacy attribute handling is done via pci_adjust_legacy_attr(), which updates dynamically allocated attributes at runtime. The upcoming conversion to static attributes needs a way to determine sparse support at visibility check time.
Add a __weak pci_legacy_has_sparse() that returns false by default. Alpha overrides it to check has_sparse() on the bus host controller.
--- arch/alpha/include/asm/pci.h | 2 ++ arch/alpha/kernel/pci-sysfs.c | 7 +++++++ drivers/pci/pci-sysfs.c | 6 ++++++ drivers/pci/pci.h | 4 ++++ 4 files changed, 19 insertions(+)
arch/alpha/include/asm/pci.h +2 -0
@@ -86,6 +86,8 @@ extern int pci_mmap_legacy_page_range(struct pci_bus *bus, enum pci_mmap_state mmap_state);extern void pci_adjust_legacy_attr (struct pci_bus *bus,enum pci_mmap_state mmap_type); +extern bool pci_legacy_has_sparse (struct pci_bus *bus, +enum pci_mmap_state type);#define HAVE_PCI_LEGACY 1extern const struct attribute_group pci_dev_resource_attr_group;
arch/alpha/kernel/pci-sysfs.c +7 -0
@@ -191,6 +191,13 @@ int pci_mmap_legacy_page_range(struct pci_bus *bus, struct vm_area_struct *vma,return hose_mmap_page_range (hose, vma, mmap_type, sparse); } +bool pci_legacy_has_sparse (struct pci_bus *bus,enum pci_mmap_state type) +{ +struct pci_controller *hose = bus->sysdata; + +return has_sparse (hose, type); +} +/** * pci_adjust_legacy_attr - adjustment of legacy file attributes * @bus: bus to create files under
drivers/pci/pci-sysfs.c +6 -0
@@ -1019,6 +1019,12 @@ static int pci_mmap_legacy_io(struct file *filp, struct kobject *kobj,return pci_mmap_legacy_page_range (bus, vma, pci_mmap_io); } +bool __weak pci_legacy_has_sparse (struct pci_bus *bus, +enum pci_mmap_state type) +{ +return false; +} +/** * pci_adjust_legacy_attr - adjustment of legacy file attributes * @b: bus to create files under
drivers/pci/pci.h +4 -0
@@ -390,6 +390,10 @@ static inline int pci_no_d1d2(struct pci_dev *dev) } +#ifdef HAVE_PCI_LEGACY +bool pci_legacy_has_sparse (struct pci_bus *bus,enum pci_mmap_state type); +#endif +#ifdef CONFIG_SYSFS extern const struct attribute_group *pci_dev_groups[];extern const struct attribute_group *pci_dev_attr_groups[];
Signature · 1 line
2.54.0
PATCH v6 22/24 PCI/sysfs: Convert legacy I/O and memory attributes to static definitions
In reply to Krzysztof WilczyńskiCurrently, legacy_io and legacy_mem are dynamically allocated and created by pci_create_legacy_files(), with pci_adjust_legacy_attr() updating the attributes at runtime on Alpha to rename them and shift the size for sparse addressing.
Convert to four static const attributes (legacy_io, legacy_io_sparse, legacy_mem, legacy_mem_sparse) with is_bin_visible() callbacks that use pci_legacy_has_sparse() to select the appropriate variant per bus. The sizes are compile-time constants and .size is set directly on each attribute.
Register the groups in pcibus_groups[] under a HAVE_PCI_LEGACY guard so the driver model handles creation and removal automatically.
Stub out pci_create_legacy_files() and pci_remove_legacy_files() as the dynamic creation is no longer needed. Remove the __weak pci_adjust_legacy_attr(), Alpha's override, and its declaration from both Alpha and PowerPC asm/pci.h headers.
--- arch/alpha/include/asm/pci.h | 2 - arch/alpha/kernel/pci-sysfs.c | 24 ---- arch/powerpc/include/asm/pci.h | 2 - drivers/pci/pci-sysfs.c | 200 ++++++++++++++++++++------------- 4 files changed, 120 insertions(+), 108 deletions(-)
arch/alpha/include/asm/pci.h +0 -2
@@ -84,8 +84,6 @@ extern int pci_legacy_write(struct pci_bus *bus, loff_t port, u32 val,extern int pci_mmap_legacy_page_range (struct pci_bus *bus,struct vm_area_struct *vma,enum pci_mmap_state mmap_state); -extern void pci_adjust_legacy_attr (struct pci_bus *bus, -enum pci_mmap_state mmap_type);extern bool pci_legacy_has_sparse (struct pci_bus *bus,enum pci_mmap_state type);#define HAVE_PCI_LEGACY 1
arch/alpha/kernel/pci-sysfs.c +0 -24
@@ -198,30 +198,6 @@ bool pci_legacy_has_sparse(struct pci_bus *bus, enum pci_mmap_state type)return has_sparse (hose, type); } -/** -* pci_adjust_legacy_attr - adjustment of legacy file attributes -* @bus: bus to create files under -* @mmap_type: I/O port or memory -* -* Adjust file name and size for sparse mappings. -*/ -void pci_adjust_legacy_attr (struct pci_bus *bus,enum pci_mmap_state mmap_type) -{ -struct pci_controller *hose = bus->sysdata; - -if (!has_sparse (hose, mmap_type)) -return ; - -if (mmap_type == pci_mmap_mem) { - bus->legacy_mem->attr.name ="legacy_mem_sparse" ; - bus->legacy_mem->size <<=5 ; - }else { - bus->legacy_io->attr.name ="legacy_io_sparse" ; - bus->legacy_io->size <<=5 ; - } -return ; -} -/* Legacy I/O bus read/write functions */ int pci_legacy_read (struct pci_bus *bus,loff_t port,u32 *val,size_t size) {
arch/powerpc/include/asm/pci.h +0 -2
@@ -82,8 +82,6 @@ extern int pci_legacy_write(struct pci_bus *bus, loff_t port, u32 val,extern int pci_mmap_legacy_page_range (struct pci_bus *bus,struct vm_area_struct *vma,enum pci_mmap_state mmap_state); -extern void pci_adjust_legacy_attr (struct pci_bus *bus, -enum pci_mmap_state mmap_type);#define HAVE_PCI_LEGACY 1extern void pcibios_claim_one_bus (struct pci_bus *b);
drivers/pci/pci-sysfs.c +120 -80
222 lines not on this page · raw message
Signature · 1 line
2.54.0
PATCH v6 23/24 PCI/sysfs: Remove pci_create_legacy_files() and pci_sysfs_init()
In reply to Krzysztof WilczyńskiCurrently, pci_create_legacy_files() and pci_remove_legacy_files() are no-op stubs. With legacy attributes now handled by static groups registered via pcibus_groups[], no call site needs them.
Remove both functions, their declarations, and the call sites in pci_register_host_bridge(), pci_alloc_child_bus(), and pci_remove_bus().
Remove the pci_sysfs_init() late_initcall and sysfs_initialized. The late_initcall originally existed to create all the dynamic PCI sysfs files, but with both resource and legacy attributes now handled by static groups, it is no longer needed.
Remove the legacy_io and legacy_mem fields from struct pci_bus which were used to track the dynamically allocated legacy attributes.
--- drivers/pci/pci-sysfs.c | 21 --------------------- drivers/pci/pci.h | 8 -------- drivers/pci/probe.c | 6 ------ drivers/pci/remove.c | 2 -- include/linux/pci.h | 2 -- 5 files changed, 39 deletions(-)
drivers/pci/pci-sysfs.c +0 -21
@@ -37,10 +37,6 @@#define ARCH_PCI_DEV_GROUPS #endif -#ifdef HAVE_PCI_LEGACY -static int sysfs_initialized;/* = 0 */ -#endif -/* show configuration fields */ #define pci_config_attr (field, format_string) \ static ssize_t \
@@ -1135,8 +1131,6 @@ static const struct attribute_group pci_legacy_mem_sparse_group = { .is_bin_visible = pci_legacy_mem_sparse_is_visible, }; -void pci_create_legacy_files (struct pci_bus *b) { } -void pci_remove_legacy_files (struct pci_bus *b) { }#endif /* HAVE_PCI_LEGACY */ const struct attribute_group *pcibus_groups[] = {
@@ -1811,21 +1805,6 @@ static const struct attribute_group pci_dev_resource_resize_attr_group = { .is_visible = resource_resize_attr_is_visible, }; -#ifdef HAVE_PCI_LEGACY -static int __init pci_sysfs_init (void ) -{ -struct pci_bus *pbus =NULL ; - - sysfs_initialized =1 ; - -while ((pbus =pci_find_next_bus (pbus))) -pci_create_legacy_files (pbus); - -return 0 ; -} -late_initcall (pci_sysfs_init); -#endif -static struct attribute *pci_dev_dev_attrs[] = { &dev_attr_boot_vga.attr, &dev_attr_serial_number.attr,
drivers/pci/pci.h +0 -8
@@ -356,14 +356,6 @@ static inline int pci_proc_detach_bus(struct pci_bus *bus) { return 0; }int pci_hp_add_bridge (struct pci_dev *dev);bool pci_hp_spurious_link_change (struct pci_dev *pdev); -#if defined(CONFIG_SYSFS ) && defined(HAVE_PCI_LEGACY ) -void pci_create_legacy_files (struct pci_bus *bus); -void pci_remove_legacy_files (struct pci_bus *bus); -#else -static inline void pci_create_legacy_files (struct pci_bus *bus) { } -static inline void pci_remove_legacy_files (struct pci_bus *bus) { } -#endif -/* Lock for read/write access to pci device and bus lists */ extern struct rw_semaphore pci_bus_sem;extern struct mutex pci_slot_mutex;
drivers/pci/probe.c +0 -6
@@ -1068,9 +1068,6 @@ static int pci_register_host_bridge(struct pci_host_bridge *bridge)dev_err (&bus->dev,"failed to add bus: %d\n" , err); } -/* Create legacy_io and legacy_mem files for this bus */ -pci_create_legacy_files (bus); -if (parent)dev_info (parent,"PCI host bridge to bus %s\n" , name);else
@@ -1276,9 +1273,6 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent,dev_err (&child->dev,"failed to add bus: %d\n" , ret); } -/* Create legacy_io and legacy_mem files for this bus */ -pci_create_legacy_files (child); -return child; }
drivers/pci/remove.c +0 -2
@@ -65,8 +65,6 @@ void pci_remove_bus(struct pci_bus *bus)list_del (&bus->node);pci_bus_release_busn_res (bus);up_write (&pci_bus_sem); -pci_remove_legacy_files (bus); -if (bus->ops->remove_bus) bus->ops->remove_bus (bus);
include/linux/pci.h +0 -2
@@ -724,8 +724,6 @@ struct pci_bus {pci_bus_flags_t bus_flags;/* Inherited by child buses */ struct device *bridge;struct device dev; -struct bin_attribute *legacy_io;/* Legacy I/O for this bus */ -struct bin_attribute *legacy_mem;/* Legacy mem */ unsigned int is_added:1; unsigned int unsafe_warn:1; /* warned about RW1C config write */ unsigned int flit_mode:1; /* Link in Flit mode */
Signature · 1 line
2.54.0
PATCH v6 24/24 PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
In reply to Krzysztof WilczyńskiThe resourceN_resize sysfs attributes allow users to resize Resizable BARs (ReBAR). After a successful resize, the resource attribute groups are removed and recreated so that the updated BAR sizes are reflected in the sysfs files.
Resizable BARs are a PCI Express extended capability (PCI_EXT_CAP_ID_REBAR), which requires PCIe extended config space.
Every PCIe-capable architecture defines either HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE (via the relevant arch headers or the generic asm-generic/pci.h fallback). On platforms that define neither, the resource files are not created and the sysfs group remove and create calls in __resource_resize_store() are no-ops.
Thus, move the resize show and store helpers, the per-BAR attribute definitions, and the attribute group behind the existing #ifdef HAVE_PCI_MMAP || ARCH_GENERIC_PCI_MMAP_RESOURCE guard, and fold the group reference in pci_dev_groups[] into the existing #if block.
--- drivers/pci/pci-sysfs.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/pci/pci-sysfs.c +3 -1
@@ -1690,6 +1690,7 @@ static const struct attribute_group pci_dev_reset_method_attr_group = { .is_visible = pci_dev_reset_attr_is_visible, }; +#if defined(HAVE_PCI_MMAP ) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )static ssize_t __resource_resize_show (struct device *dev,int n,char *buf) {struct pci_dev *pdev =to_pci_dev (dev);
@@ -1804,6 +1805,7 @@ static const struct attribute_group pci_dev_resource_resize_attr_group = { .attrs = resource_resize_attrs, .is_visible = resource_resize_attr_is_visible, }; +#endif static struct attribute *pci_dev_dev_attrs[] = { &dev_attr_boot_vga.attr,
@@ -1878,8 +1880,8 @@ const struct attribute_group *pci_dev_groups[] = { &pci_dev_resource_io_attr_group, &pci_dev_resource_uc_attr_group, &pci_dev_resource_wc_attr_group, -#endif &pci_dev_resource_resize_attr_group, +#endif &pci_dev_config_attr_group, &pci_dev_rom_attr_group, &pci_dev_reset_attr_group,
Signature · 1 line
2.54.0
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Quoted 4 lines · Krzysztof Wilczyński
The
resourceN_resizesysfs attributes allow users to resize Resizable BARs (ReBAR). After a successful resize, the resource attribute groups are removed and recreated so that the updated BAR sizes are reflected in the sysfs files.
Out of curiosity, where does this removal/recreation happen? I don't see it in pci_resize_resource() or pci_do_resource_release_and_resize().
Quoted 3 lines
Resizable BARs are a PCI Express extended capability (
PCI_EXT_CAP_ID_REBAR), which requires PCIe extended config space.
It sounds like the fact that ReBAR requires extended config space is important somehow (beyond just the fact that we can't discover ReBAR without it)? Is there some connection between extended config space and mmap?
Quoted 6 lines
Every PCIe-capable architecture defines either
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE(via the relevant arch headers or the genericasm-generic/pci.hfallback). On platforms that define neither, the resource files are not created and the sysfs group remove and create calls in__resource_resize_store()are no-ops.
What's the connection between ReBAR and mmap?
Quoted 43 lines
Thus, move the resize show and store helpers, the per-BAR attribute definitions, and the attribute group behind the existing #ifdef
HAVE_PCI_MMAP||ARCH_GENERIC_PCI_MMAP_RESOURCEguard, and fold the group reference in pci_dev_groups[] into the existing #if block.Signed-off-by Krzysztof Wilczyński <[email protected]>--- drivers/pci/pci-sysfs.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)drivers/pci/pci-sysfs.c +3
-1@@ -1690,6 +1690,7 @@ static const struct attribute_group pci_dev_reset_method_attr_group = { .is_visible = pci_dev_reset_attr_is_visible, }; +#if defined(HAVE_PCI_MMAP ) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE )static ssize_t __resource_resize_show (struct device *dev,int n,char *buf) {struct pci_dev *pdev =to_pci_dev (dev);@@ -1804,6 +1805,7 @@ static const struct attribute_group pci_dev_resource_resize_attr_group = { .attrs = resource_resize_attrs, .is_visible = resource_resize_attr_is_visible, }; +#endif static struct attribute *pci_dev_dev_attrs[] = { &dev_attr_boot_vga.attr,@@ -1878,8 +1880,8 @@ const struct attribute_group *pci_dev_groups[] = { &pci_dev_resource_io_attr_group, &pci_dev_resource_uc_attr_group, &pci_dev_resource_wc_attr_group, -#endif &pci_dev_resource_resize_attr_group, +#endif &pci_dev_config_attr_group, &pci_dev_rom_attr_group, &pci_dev_reset_attr_group,Signature · 1 line
2.54.0
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Hello,
Quoted 8 lines
Quoted 4 lines
The
resourceN_resizesysfs attributes allow users to resize Resizable BARs (ReBAR). After a successful resize, the resource attribute groups are removed and recreated so that the updated BAR sizes are reflected in the sysfs files.Out of curiosity, where does this removal/recreation happen? I don't see it in
pci_resize_resource()orpci_do_resource_release_and_resize().
The __resource_resize_store() helper carries the relevant code, per:
sysfs_remove_groups(&pdev->dev.kobj, pci_dev_resource_attr_groups); ret = pci_resize_resource(pdev, n, size, 0); if (ret) pci_warn(pdev, "Failed to resize BAR %d: %pe\n", n, ERR_PTR(ret)); pci_assign_unassigned_bus_resources(bus);
if (sysfs_create_groups(&pdev->dev.kobj, pci_dev_resource_attr_groups))
pci_warn(pdev, "Failed to recreate resource groups after BAR resizing\n");
pci_write_config_word(pdev, PCI_COMMAND, cmd);
This takes place under the device_lock() with a given device woken up using pci_config_pm_runtime_get().
See for reference:
https://elixir.bootlin.com/linux/v7.0.1/source/drivers/pci/pci-sysfs.c#L1596
Quoted 8 lines
Quoted 3 lines
Resizable BARs are a PCI Express extended capability (
PCI_EXT_CAP_ID_REBAR), which requires PCIe extended config space.It sounds like the fact that ReBAR requires extended config space is important somehow (beyond just the fact that we can't discover ReBAR without it)? Is there some connection between extended config space and mmap?
No, there is no connection between extended configuration space and mmap.
I was trying to establish two separate facts:
- ReBAR requires PCI Express (for the extended configuration space support).
- Every PCI Express-capable architecture defines either HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE.
The commit message should have captured the reasoning better.
Quoted 8 lines
Quoted 6 lines
Every PCIe-capable architecture defines either
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE(via the relevant arch headers or the genericasm-generic/pci.hfallback). On platforms that define neither, the resource files are not created and the sysfs group remove and create calls in__resource_resize_store()are no-ops.What's the connection between ReBAR and mmap?
The connection is somewhat indirect, through the sysfs resource files.
The resourceN_resize attribute exists so userspace can resize a BAR and then access it through the resourceN sysfs files. Those resource files only exist on platforms that define HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE.
On architectures without either of these defines, pci_dev_resource_attr_groups array will be NULL and the sysfs_remove_groups() and sysfs_create_groups() calls in __resource_resize_store() are no-ops. And there will be no resource files to tear down or recreate.
To add, there are some kernel drivers that need ReBAR call pci_resize_resource() directly (e.g., amdgpu, xe, i915), not through the sysfs attribute.
The only platform without these aforementioned defines is Alpha, which is conventional PCI only and cannot have ReBAR. So this guard removes dead sysfs code on platforms where it can never be executed.
Hope this helps.
Thank you!
Krzysztof
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Hello,
Quoted 3 lines
The only platform without these aforementioned defines is Alpha, which is conventional PCI only and cannot have ReBAR. So this guard removes dead sysfs code on platforms where it can never be executed.
Having a closer look:
resource_resize_attr_is_visible()
pci_rebar_get_current_size() <- returns -ENOTSUPP, so is_visible callback returns 0
pci_rebar_find_pos()
pos = pdev->rebar_cap <- set to 0 on a conventional PCI
if (!pos)
return -ENOTSUPP <- no ReBAR support
The pdev->rebar_cap is set during PCI enumeration:
pci_init_capabilities()
pci_rebar_init()
pdev->rebar_cap = pci_find_ext_capability()
pci_find_next_ext_capability()
if (dev->cfg_size <= PCI_CFG_SPACE_SIZE)
return 0; <- dev->cfg_size set to 256 here for conventional PCIThe PCI_CFG_SPACE_SIZE is 256 here.
When the platform has support for PCI Express, the dev->cfg_size is then set to 4096. On an architecture that supports conventional PCI only (such as Alpha), the pdev->rebar_cap will be set to 0, the is_visible callback will then return 0, and the resize sysfs attribute is never created, as such, the __resource_resize_store() callback will never be executed.
To make the connetion here to the #ifdef guards:
For the pci_rebar_get_current_size() to return >= 0, the device needs PCI Express and extended configuration space support. As of today, every architecture with PCI Express support defines HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE.
I hope the reasoning here works.
Thank you!
Krzysztof
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Quoted 32 lines · Krzysztof Wilczyński
Hello,
Quoted 3 lines
The only platform without these aforementioned defines is Alpha, which is conventional PCI only and cannot have ReBAR. So this guard removes dead sysfs code on platforms where it can never be executed.
Having a closer look:
resource_resize_attr_is_visible()
pci_rebar_get_current_size()<- returns-ENOTSUPP, sois_visiblecallback returns 0
pci_rebar_find_pos()
pos =pdev->rebar_cap<- set to 0 on a conventional PCI
if (!pos)
return-ENOTSUPP<- no ReBAR supportThe
pdev->rebar_capis set during PCI enumeration:
pci_init_capabilities()pci_rebar_init() pdev->rebar_cap = pci_find_ext_capability() pci_find_next_ext_capability() if (dev->cfg_size <= PCI_CFG_SPACE_SIZE) return 0; <- dev->cfg_size set to 256 here for conventional PCIThe
PCI_CFG_SPACE_SIZEis 256 here.When the platform has support for PCI Express, the
dev->cfg_sizeis then set to 4096. On an architecture that supports conventional PCI only (such as Alpha), thepdev->rebar_capwill be set to 0, theis_visiblecallback will then return 0, and the resize sysfs attribute is never created, as such, the__resource_resize_store()callback will never be executed.
Quoted 8 lines
To make the connetion here to the #ifdef guards:
For the
pci_rebar_get_current_size()to return >= 0, the device needs PCI Express and extended configuration space support. As of today, every architecture with PCI Express support definesHAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE.I hope the reasoning here works.
We're talking about this #ifdef:
+#if defined(HAVE_PCI_MMAP) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE) static ssize_t __resource_resize_show(struct device *dev, int n, char *buf) ... +#endif
I follow the reasoning now but by next week I won't, so I think it requires too much background knowledge. Future changes involving HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE could easily break this.
IIUC it's basically doing what "#ifdef CONFIG_PCI_REBAR" or even "#ifdef CONFIG_PCI_EXPRESS" would do, if we had such a thing.
How terrible would it be if we just accepted this dead code on Alpha?
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Hello,
Quoted 46 lines
Quoted 30 lines
Quoted 3 lines
The only platform without these aforementioned defines is Alpha, which is conventional PCI only and cannot have ReBAR. So this guard removes dead sysfs code on platforms where it can never be executed.
Having a closer look:
resource_resize_attr_is_visible()
pci_rebar_get_current_size()<- returns-ENOTSUPP, sois_visiblecallback returns 0
pci_rebar_find_pos()
pos =pdev->rebar_cap<- set to 0 on a conventional PCI
if (!pos)
return-ENOTSUPP<- no ReBAR supportThe
pdev->rebar_capis set during PCI enumeration:
pci_init_capabilities()pci_rebar_init() pdev->rebar_cap = pci_find_ext_capability() pci_find_next_ext_capability() if (dev->cfg_size <= PCI_CFG_SPACE_SIZE) return 0; <- dev->cfg_size set to 256 here for conventional PCIThe
PCI_CFG_SPACE_SIZEis 256 here.When the platform has support for PCI Express, the
dev->cfg_sizeis then set to 4096. On an architecture that supports conventional PCI only (such as Alpha), thepdev->rebar_capwill be set to 0, theis_visiblecallback will then return 0, and the resize sysfs attribute is never created, as such, the__resource_resize_store()callback will never be executed.Quoted 8 lines
To make the connetion here to the #ifdef guards:
For the
pci_rebar_get_current_size()to return >= 0, the device needs PCI Express and extended configuration space support. As of today, every architecture with PCI Express support definesHAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE.I hope the reasoning here works.
We're talking about this #ifdef:
+#if defined(HAVE_PCI_MMAP) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE) static ssize_t __resource_resize_show(struct device *dev, int n, char *buf) ... +#endif
Quoted 7 lines
I follow the reasoning now but by next week I won't, so I think it requires too much background knowledge. Future changes involving
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCEcould easily break this.IIUC it's basically doing what "#ifdef
CONFIG_PCI_REBAR" or even "#ifdefCONFIG_PCI_EXPRESS" would do, if we had such a thing.
We don't sadly have such guards at the moment, so using the guards like HAVE_PCI_MMAP or ARCH_GENERIC_PCI_MMAP_RESOURCE would be the next best thing. We already rely on these throughout the pci-sysfs.c already, and will also rely on either for the static sysfs attributes, so if there was some issues with either of these, if these "broke" somehow, then we would have other more severe problems. Note, that architectures rely on these macros to let us know about what "feature" is expected to be enabled, so to speak, so I would imagine nobody would break this accidentally (famous last words) and perhaps with extreme caution would do it on purpose.
Quoted 1 line
How terrible would it be if we just accepted this dead code on Alpha?
I would prefer not to build any dead code anywhere if it can be helped, especially with as little as two lines of code added. Plus, most of the code setting up resources that are not specific to Alpha, would have been disabled using exactly the same guard as the one proposed to be added here, not like this sets any precedent or adds something new.
That being said, I will drop this from the next version.
Thank you!
Krzysztof
Re: [PATCH v6 24/24] PCI/sysfs: Limit BAR resize attribute scope to platforms with PCI mmap
Quoted 64 lines · Krzysztof Wilczyński
Quoted 46 lines
Quoted 30 lines
Quoted 3 lines
The only platform without these aforementioned defines is Alpha, which is conventional PCI only and cannot have ReBAR. So this guard removes dead sysfs code on platforms where it can never be executed.
Having a closer look:
resource_resize_attr_is_visible()
pci_rebar_get_current_size()<- returns-ENOTSUPP, sois_visiblecallback returns 0
pci_rebar_find_pos()
pos =pdev->rebar_cap<- set to 0 on a conventional PCI
if (!pos)
return-ENOTSUPP<- no ReBAR supportThe
pdev->rebar_capis set during PCI enumeration:
pci_init_capabilities()pci_rebar_init() pdev->rebar_cap = pci_find_ext_capability() pci_find_next_ext_capability() if (dev->cfg_size <= PCI_CFG_SPACE_SIZE) return 0; <- dev->cfg_size set to 256 here for conventional PCIThe
PCI_CFG_SPACE_SIZEis 256 here.When the platform has support for PCI Express, the
dev->cfg_sizeis then set to 4096. On an architecture that supports conventional PCI only (such as Alpha), thepdev->rebar_capwill be set to 0, theis_visiblecallback will then return 0, and the resize sysfs attribute is never created, as such, the__resource_resize_store()callback will never be executed.Quoted 8 lines
To make the connetion here to the #ifdef guards:
For the
pci_rebar_get_current_size()to return >= 0, the device needs PCI Express and extended configuration space support. As of today, every architecture with PCI Express support definesHAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCE.I hope the reasoning here works.
We're talking about this #ifdef:
+#if defined(HAVE_PCI_MMAP) || defined(ARCH_GENERIC_PCI_MMAP_RESOURCE) static ssize_t __resource_resize_show(struct device *dev, int n, char *buf) ... +#endifQuoted 7 lines
I follow the reasoning now but by next week I won't, so I think it requires too much background knowledge. Future changes involving
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCEcould easily break this.IIUC it's basically doing what "#ifdef
CONFIG_PCI_REBAR" or even "#ifdefCONFIG_PCI_EXPRESS" would do, if we had such a thing.We don't sadly have such guards at the moment, so using the guards like
HAVE_PCI_MMAPorARCH_GENERIC_PCI_MMAP_RESOURCEwould be the next best thing. We already rely on these throughout thepci-sysfs.calready, and will also rely on either for the static sysfs attributes, so if there was some issues with either of these, if these "broke" somehow, then we would have other more severe problems. Note, that architectures rely on these macros to let us know about what "feature" is expected to be enabled, so to speak, so I would imagine nobody would break this accidentally (famous last words) and perhaps with extreme caution would do it on purpose.
Quoted 7 lines
Quoted 1 line
How terrible would it be if we just accepted this dead code on Alpha?
I would prefer not to build any dead code anywhere if it can be helped, especially with as little as two lines of code added. Plus, most of the code setting up resources that are not specific to Alpha, would have been disabled using exactly the same guard as the one proposed to be added here, not like this sets any precedent or adds something new.
OK, let's leave it as-is. It's confusing to read, but no more so than other existing uses.
Hello,
Quoted 4 lines
This series converts every dynamically allocated PCI sysfs attribute to a static const definition. After the full series,
pci_sysfs_init()andsysfs_initializedare gone, and every sysfs file is created by the driver model atdevice_add()time.
A note on testing:
0-day bot (recent test runs; newer builds will arrive later):
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
KernelCI (for the "for-kernelci" branch):
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/941dd7c3e16840724dc961f10b84e193d13cdb57
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/683e66b11da157f730101f6919c7468a09cf3e3f
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/209e2cfd205a8aad4bae32e6f82b96b20902aa74
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/70293477e2c0ae8cbc250098818e726e1d658b53
- https://dashboard.kernelci.org/tree?ts=pci
Sashiko's feedback:
- https://sashiko.dev/#/patchset/20260422161407.118748-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260416180107.777065-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org
I sadly do not own any Alpha or PowerPC hardware, so when I was testing these architectures while working on the series, it would be only under QEMU.
That said, Magnus Lindholm was able to test the series on the Alpha hardware he owns, see:
- https://lore.kernel.org/linux-pci/CA+=Fv5Q1tZQwnanw99NbvzT-QenfYz7vUdY02_TuPqHX32ZAiA@mail.gmail.com
Lorenzo Pieralisi did some testing reported outside the mailing list (we talked on IRC), on the platform he had issues before, and while the issues were more with procfs races, similar to the sysfs ones this series aims to fix, he didn't notice regressions when having this series applied.
Thank you!
Krzysztof
Quoted 26 lines · Krzysztof Wilczyński
Hello,
Quoted 4 lines
This series converts every dynamically allocated PCI sysfs attribute to a static const definition. After the full series,
pci_sysfs_init()andsysfs_initializedare gone, and every sysfs file is created by the driver model atdevice_add()time.A note on testing:
0-day bot (recent test runs; newer builds will arrive later):
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]KernelCI (for the "for-kernelci" branch):
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/941dd7c3e16840724dc961f10b84e193d13cdb57
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/683e66b11da157f730101f6919c7468a09cf3e3f
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/209e2cfd205a8aad4bae32e6f82b96b20902aa74
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/70293477e2c0ae8cbc250098818e726e1d658b53
- https://dashboard.kernelci.org/tree?ts=pci
Quoted 5 lines
Sashiko's feedback:
- https://sashiko.dev/#/patchset/20260422161407.118748-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260416180107.777065-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org
Thanks for all this work! I think this will be a great step forward. I assume you've probably looked at the sashiko feedback and concluded that no changes are needed, e.g., the feedback is out of scope for this series? Your thoughts there would help me out.
Quoted 17 lines
I sadly do not own any Alpha or PowerPC hardware, so when I was testing these architectures while working on the series, it would be only under QEMU.
That said, Magnus Lindholm was able to test the series on the Alpha hardware he owns, see:
- https://lore.kernel.org/linux-pci/CA+=Fv5Q1tZQwnanw99NbvzT-QenfYz7vUdY02_TuPqHX32ZAiA@mail.gmail.com
Lorenzo Pieralisi did some testing reported outside the mailing list (we talked on IRC), on the platform he had issues before, and while the issues were more with procfs races, similar to the sysfs ones this series aims to fix, he didn't notice regressions when having this series applied.
Thank you!
Krzysztof
Hello,
Quoted 10 lines
Quoted 5 lines
Sashiko's feedback:
- https://sashiko.dev/#/patchset/20260422161407.118748-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260416180107.777065-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.orgThanks for all this work! I think this will be a great step forward. I assume you've probably looked at the sashiko feedback and concluded that no changes are needed, e.g., the feedback is out of scope for this series? Your thoughts there would help me out.
The only actionable feedback would be to update commit message of patch 18, so that it mentions pci_stop_dev() rather than pci_stop_bus_device(), something we can do later.
One could also drop #if guard from the struct pci_dev as added in the patch 9, which is later removed completely anyway. There is no ODR violation or ABI break there.
We won't be fixing any more kernel lock-down issues at this time, and the value of legacy I/O space size (the 0xffff) is something that was there from 2005, so not something this series introduced or changed.
Using HAVE_PCI_MMAP and/or ARCH_GENERIC_PCI_MMAP_RESOURCE to stop the resizable BAR resources from being included on platforms that do not provide either, like Alpha, should not be a problem.
So, no. No serious issues there. But let me know if you want to change something, so I can send next version if needed.
Thank you!
Krzysztof
Shivaprasad G Bhat
Tested-byHi Krzysztof,
Quoted 31 lines · Krzysztof Wilczyński
Hello,
Quoted 4 lines
This series converts every dynamically allocated PCI sysfs attribute to a static const definition. After the full series,
pci_sysfs_init()andsysfs_initializedare gone, and every sysfs file is created by the driver model atdevice_add()time.A note on testing:
0-day bot (recent test runs; newer builds will arrive later):
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]
- https://lore.kernel.org/linux-pci/[email protected]KernelCI (for the "for-kernelci" branch):
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/941dd7c3e16840724dc961f10b84e193d13cdb57
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/683e66b11da157f730101f6919c7468a09cf3e3f
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/209e2cfd205a8aad4bae32e6f82b96b20902aa74
- https://dashboard.kernelci.org/tree/linux-pci/for-kernelci/70293477e2c0ae8cbc250098818e726e1d658b53
- https://dashboard.kernelci.org/tree?ts=pciSashiko's feedback:
- https://sashiko.dev/#/patchset/20260422161407.118748-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260416180107.777065-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260411080148.471335-1-kwilczynski%40kernel.org
- https://sashiko.dev/#/patchset/20260410055040.39233-1-kwilczynski%40kernel.org
Quoted 3 lines
I sadly do not own any Alpha or PowerPC hardware, so when I was testing these architectures while working on the series, it would be only under QEMU.
I tested the patches on PPC64 machines running as pSeries(on PowerVM and KVM) also PowerNV.
The sysfs attributes looks normal on boot, and on hotplug/unplug of devices and SRIOV use cases.
I see no warnings/errors in dmesg during PCI scans, initialization.
Thanks,
Shivaprasad
Quoted 14 lines
That said, Magnus Lindholm was able to test the series on the Alpha hardware he owns, see:
- https://lore.kernel.org/linux-pci/CA+=Fv5Q1tZQwnanw99NbvzT-QenfYz7vUdY02_TuPqHX32ZAiA@mail.gmail.com
Lorenzo Pieralisi did some testing reported outside the mailing list (we talked on IRC), on the platform he had issues before, and while the issues were more with procfs races, similar to the sysfs ones this series aims to fix, he didn't notice regressions when having this series applied.
Thank you!
Krzysztof
Hello,
Quoted 11 lines
Quoted 3 lines
I sadly do not own any Alpha or PowerPC hardware, so when I was testing these architectures while working on the series, it would be only under QEMU.
I tested the patches on PPC64 machines running as pSeries(on PowerVM and KVM) also PowerNV.
The sysfs attributes looks normal on boot, and on hotplug/unplug of devices and SRIOV use cases.
I see no warnings/errors in dmesg during PCI scans, initialization.
I appreciate that you took the time to test this on a real hardware.
Quoted 1 line
Tested-by Shivaprasad G Bhat <[email protected]>
Thank you!
Krzysztof
[+cc moubingquan, Ian, Koba, Krzysztof H, Koen, Pali, Artem, Korneliusz, Alexander
+bcc vsd
in case any of you can verify that this fixes the issue you reported]
Quoted 77 lines · Krzysztof Wilczyński
Hello,
This series converts every dynamically allocated PCI sysfs attribute to a static const definition. After the full series,
pci_sysfs_init()andsysfs_initializedare gone, and every sysfs file is created by the driver model atdevice_add()time.Currently, the PCI resource files (resourceN,
resourceN_wc) and the legacy bus files (legacy_io,legacy_mem) are created dynamically from two unsynchronised paths:Path A:
late_initcall
pci_sysfs_init(late_initcall)
sysfs_initialized= 1
for_each_pci_dev
pci_create_sysfs_dev_files
sysfs_create_bin_file(resourceN,resourceN_wc)
pci_find_next_bus
pci_create_legacy_files
sysfs_create_bin_file(legacy_io,legacy_mem)Path B: device registration / hotplug
pci_bus_add_devices
pci_bus_add_device
pci_create_sysfs_dev_files
if (!sysfs_initialized) return <- only guard
sysfs_create_bin_file(resourceN,resourceN_wc)On most ACPI systems this does not race because PCI enumeration completes at
subsys_initcalltime, beforepci_sysfs_init()runs:
subsys_initcall(level 4):
acpi_pci_root_add
pci_bus_add_device
pci_create_sysfs_dev_files
if (!sysfs_initialized) <- not yet set
return-EACCES
late_initcall(level 7):
pci_sysfs_init
sysfs_initialized= 1
for_each_pci_dev
pci_create_sysfs_dev_files<- creates the files, no raceOn Devicetree platforms the host controller is a platform driver that probes via the driver model, often on a workqueue, and overlaps with the
late_initcall:CPU 0 (
late_initcall) CPU 1 (driver probe)
--------------------------- ----------------------------
pci_sysfs_init()
sysfs_initialized= 1
for_each_pci_dev(pdev)pci_bus_add_device(pdev)
pci_create_sysfs_dev_files()pci_create_sysfs_dev_files()
sysfs_create_bin_file()sysfs_create_bin_file()
-> "duplicate filename"The same happens on ACPI when probing is asynchronous (
hv_pcion Azure, RISC-V with ACPI).The duplicate causes
sysfs_create_bin_file()to fail with-EEXIST.pci_create_resource_files()then callspci_remove_resource_files()in its error unwind, tearing down files the other thread created and still references through pdev->res_attr[]. This has caused kernel panics on i.MX6 and boot failures on other platforms.Several different fixes have been proposed over the years: reordering the
sysfs_initializedassignment, adding locks, checkingpci_dev_is_added(), setting pdev->res_attr[] to NULL after kfree (which only prevents a double-free on the teardown path, not the error unwind removing the other thread's files). None would address the root cause.This has been reported a few times:
Quoted 10 lines
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/SY0P300MB04687548090B73E40AF97D8897B82@SY0P300MB0468.AUSP300.PROD.OUTLOOK.COM/
- https://lore.kernel.org/linux-pci/20230105174736.GA1154719@bhelgaas/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/20200716110423.xtfyb3n6tn5ixedh@pali/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://bugzilla.kernel.org/show_bug.cgi?id=215515
- https://bugzilla.kernel.org/show_bug.cgi?id=216888
Seems like some or all of these should be mentioned in the relevant patch as "Closes:" tags?
Quoted 3 lines
With static attributes the driver model creates sysfs entries once per device at
device_add()time, under the device lock, eliminating thelate_initcalliteration and the race along with it.
Hello,
Quoted 13 lines
Quoted 12 lines
This has been reported a few times:
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/SY0P300MB04687548090B73E40AF97D8897B82@SY0P300MB0468.AUSP300.PROD.OUTLOOK.COM/
- https://lore.kernel.org/linux-pci/20230105174736.GA1154719@bhelgaas/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://lore.kernel.org/linux-pci/20200716110423.xtfyb3n6tn5ixedh@pali/
- https://lore.kernel.org/linux-pci/[email protected]/
- https://bugzilla.kernel.org/show_bug.cgi?id=215515
- https://bugzilla.kernel.org/show_bug.cgi?id=216888
Quoted 2 lines
Seems like some or all of these should be mentioned in the relevant patch as "Closes:" tags?
Bugzilla would makes sense. As for the lore.kernel.org links, then if you find these useful when included, then add these too. Surprisingly, not as popular to do so, as I thought, per:
$ git log | grep -E 'Closes: (http?://)?lore' | wc -l 43
Having said that, the following bug looks like it might be out of scope for us, for this series aims to fix, after having a second look at it:
https://bugzilla.kernel.org/show_bug.cgi?id=216888
Thank you!
Krzysztof