From: patchwork-bot+netdevbpf@kernel.org
To: Nelson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Shannon <shannon.nelson@amd.com>
Cc: andrew+netdev@lunn.ch, brett.creeley@amd.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net] pds_core: remove write-after-free of client_id
Date: Mon, 28 Apr 2025 23:00:45 +0000 [thread overview]
Message-ID: <174588124556.1071900.9575309402812835802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250425203857.71547-1-shannon.nelson@amd.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Apr 2025 13:38:57 -0700 you wrote:
> A use-after-free error popped up in stress testing:
>
> [Mon Apr 21 21:21:33 2025] BUG: KFENCE: use-after-free write in pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
> [Mon Apr 21 21:21:33 2025] Use-after-free write at 0x000000007013ecd1 (in kfence-#47):
> [Mon Apr 21 21:21:33 2025] pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
> [Mon Apr 21 21:21:33 2025] pdsc_remove+0xc0/0x1b0 [pds_core]
> [Mon Apr 21 21:21:33 2025] pci_device_remove+0x24/0x70
> [Mon Apr 21 21:21:33 2025] device_release_driver_internal+0x11f/0x180
> [Mon Apr 21 21:21:33 2025] driver_detach+0x45/0x80
> [Mon Apr 21 21:21:33 2025] bus_remove_driver+0x83/0xe0
> [Mon Apr 21 21:21:33 2025] pci_unregister_driver+0x1a/0x80
>
> [...]
Here is the summary with links:
- [net] pds_core: remove write-after-free of client_id
https://git.kernel.org/netdev/net/c/dfd76010f8e8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-28 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 20:38 [PATCH net] pds_core: remove write-after-free of client_id Shannon Nelson
2025-04-28 19:21 ` Simon Horman
2025-04-28 23:00 ` patchwork-bot+netdevbpf [this message]
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=174588124556.1071900.9575309402812835802.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Nelson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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