mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: duziming <duziming2@huawei.com>
To: <bhelgaas@google.com>, <kwilczynski@kernel.org>
Cc: <rientjes@google.com>, <gregkh@suse.de>, <iweiny@kernel.org>,
	<djbw@kernel.org>, <Jonathan.Cameron@huawei.com>,
	<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<liuyongqiang13@huawei.com>
Subject: Re: [PING] PCI: Fix procfs PCI config access issues
Date: Mon, 12 Oct 2026 10:27:48 +0800	[thread overview]
Message-ID: <19776b93-8c12-4c08-8237-a9c08385b511@huawei.com> (raw)
In-Reply-To: <14cd77b6-5541-4134-af52-62fb1d3664a0@huawei.com>


在 2026/8/17 14:22, duziming 写道:
>
> 在 2026/7/30 11:24, Ziming Du 写道:
>> Hi,
>>
>> As suggested by Bjorn and Krzysztof, this series aligns the procfs PCI
>> configuration access implementation with its sysfs counterpart and fixes
>> issues found while reviewing the two paths.
>>
>> The first four patches fix the offset truncation, inode size update 
>> race,
>> missing driver-exclusive resource warning, and unnecessary runtime PM
>> operations at the end of sysfs configuration space. The final two
>> patches align the procfs read and write implementations with their sysfs
>> counterparts.
>>
>> Changes from v1:
>>    - Merge the read and write offset fixes and move them before the
>>      refactoring to avoid an intermediate signed/unsigned regression.
>>    - Serialize i_size_write() with the inode lock.
>>    - Add the driver-exclusive resource warning to procfs writes.
>>    - Avoid unnecessary runtime PM get/put when sysfs config access 
>> starts at EOF.
>>
>> Link: https://lore.kernel.org/all/20260303193253.GA3817951@bhelgaas/
>> Link: 
>> https://lore.kernel.org/linux-pci/20260414024544.2975605-1-duziming2@huawei.com/
>> Link: 
>> https://sashiko.dev/#/patchset/20260414024544.2975605-1-duziming2%40huawei.com
>>
>>
>> Ziming Du (6):
>>    PCI: Prevent overflow in proc_bus_pci_{read,write}()
>>    PCI/proc: Serialize config inode size updates
>>    PCI/proc: Warn on writes to driver-exclusive config regions
>>    PCI/sysfs: Avoid runtime PM at config-space EOF
>>    PCI: Align proc_bus_pci_write() with pci_write_config()
>>    PCI: Align proc_bus_pci_read() with pci_read_config()
>>
>>   drivers/pci/pci-sysfs.c |   4 +-
>>   drivers/pci/proc.c      | 124 +++++++++++++++++++++-------------------
>>   2 files changed, 68 insertions(+), 60 deletions(-)
>
> Hi,
>
> Gentle ping on this patch.
>
> Thanks
>
> Ziming

Hi all,

Just gently bumping this patch to the top of your inbox.

I would really appreciate any feedback, review, or thoughts when you 
have some spare cycles.

Thanks, Ziming


  reply	other threads:[~2026-10-12  2:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  3:24 [PATCH v2 0/6] " Ziming Du
2026-07-30  3:24 ` [PATCH v2 1/6] PCI: Prevent overflow in proc_bus_pci_{read,write}() Ziming Du
2026-07-30  3:24 ` [PATCH v2 2/6] PCI/proc: Serialize config inode size updates Ziming Du
2026-07-30  3:24 ` [PATCH v2 3/6] PCI/proc: Warn on writes to driver-exclusive config regions Ziming Du
2026-07-30  3:24 ` [PATCH v2 4/6] PCI/sysfs: Avoid runtime PM at config-space EOF Ziming Du
2026-07-30  3:24 ` [PATCH v2 5/6] PCI: Align proc_bus_pci_write() with pci_write_config() Ziming Du
2026-07-30  3:24 ` [PATCH v2 6/6] PCI: Align proc_bus_pci_read() with pci_read_config() Ziming Du
2026-08-17  6:22 ` [PING] PCI: Fix procfs PCI config access issues duziming
2026-10-12  2:27   ` duziming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-14  2:45 [PATCH 0/4] " Ziming Du
2026-04-27  2:22 ` [PING] " duziming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19776b93-8c12-4c08-8237-a9c08385b511@huawei.com \
    --to=duziming2@huawei.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=djbw@kernel.org \
    --cc=gregkh@suse.de \
    --cc=iweiny@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuyongqiang13@huawei.com \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®