mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: duziming <duziming2@huawei.com>
To: <duziming2@huawei.com>
Cc: <alex@shazbot.org>, <bhelgaas@google.com>, <chrisw@redhat.com>,
	<jbarnes@virtuousgeek.org>, <linux-kernel@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <liuyongqiang13@huawei.com>,
	<duziming2@huawei.com>
Subject: Re: [PATCH v4 0/4] Miscellaneous fixes for pci subsystem
Date: Fri, 30 Jan 2026 15:53:10 +0800	[thread overview]
Message-ID: <728a9d24-b2cc-43f3-a1c3-12695155bf2f@huawei.com> (raw)
In-Reply-To: <20260116081723.1603603-1-duziming2@huawei.com>

Hi all,

Gentle ping on this patchset. Any feedback would be greatly appreciated.

On 2026/1/15 15:52, Ziming Du wrote:

> Miscellaneous fixes for pci subsystem
>
> Changes in v4:
> - Remove the architecture-specific #ifdef to apply the alignment
>    check for all platforms (including x86), as device registers are
>    naturally aligned anyway.
> - Fix a potential issue in proc_bus_pci_read() to make it consistent
>    with proc_bus_pci_write(), as suggested by Ilpo Järvinen.
> - Link to v3:https://lore.kernel.org/linux-pci/20260108015944.3520719-1-duziming2@huawei.com/
>
> Changes in v3:
> - Check *ppos before assign it to pos.
> - Link to v2:https://lore.kernel.org/linux-pci/20251224092721.2034529-1-duziming2@huawei.com/
>
> Changes in v2:
> - Correct grammer and indentation.
> - Remove unrelated stack traces from the commit message.
> - Modify the handling of pos by adding a non-negative check to ensure
>    that the input value is valid.
> - Use the existing IS_ALIGNED macro and ensure that after modification,
>    other cases still retuen -EINVAL as before.
> - Link to v1:https://lore.kernel.org/linux-pci/20251216083912.758219-1-duziming2@huawei.com/
>
> Yongqiang Liu (2):
>    PCI: Prevent overflow in proc_bus_pci_write()
>    PCI/sysfs: Prohibit unaligned access to I/O port
> Ziming Du (2):
>    PCI/sysfs: Fix null pointer dereference during hotplug
>    PCI: Prevent overflow in proc_bus_pci_read()
>
>   drivers/pci/pci-sysfs.c |  7 +++++++
>   drivers/pci/proc.c      | 11 +++++++++--
>   2 files changed, 16 insertions(+), 2 deletions(-)

Thanx du!


  parent reply	other threads:[~2026-01-30  7:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  8:17 Ziming Du
2026-01-16  8:17 ` [PATCH v4 1/4] PCI/sysfs: Prohibit unaligned access to I/O port Ziming Du
2026-02-26 17:00   ` Bjorn Helgaas
2026-01-16  8:17 ` [PATCH v4 2/4] PCI/sysfs: Fix null pointer dereference during hotplug Ziming Du
2026-02-26 17:14   ` Bjorn Helgaas
2026-02-27  2:30     ` duziming
2026-04-02  7:23     ` duziming
2026-05-02 16:24       ` Krzysztof Wilczyński
2026-01-16  8:17 ` [PATCH v4 3/4] PCI: Prevent overflow in proc_bus_pci_write() Ziming Du
2026-03-03 19:32   ` Bjorn Helgaas
2026-01-16  8:17 ` [PATCH v4 4/4] PCI: Prevent overflow in proc_bus_pci_read() Ziming Du
2026-01-30  7:53 ` duziming [this message]
2026-02-06 22:29   ` [PATCH v4 0/4] Miscellaneous fixes for pci subsystem Bjorn Helgaas
2026-02-26  9:07     ` 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=728a9d24-b2cc-43f3-a1c3-12695155bf2f@huawei.com \
    --to=duziming2@huawei.com \
    --cc=alex@shazbot.org \
    --cc=bhelgaas@google.com \
    --cc=chrisw@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuyongqiang13@huawei.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®