From: patchwork-bot+netdevbpf@kernel.org
To: Cosmin Ratiu <cratiu@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, andrew+netdev@lunn.ch, pabeni@redhat.com,
jdamato@fastly.com, shuah@kernel.org, sdf@fomichev.me,
almasrymina@google.com, saeedm@nvidia.com, tariqt@nvidia.com,
dtatulea@nvidia.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2] tests/ncdevmem: Fix double-free of queue array
Date: Fri, 09 May 2025 23:30:31 +0000 [thread overview]
Message-ID: <174683343176.3841790.11524144387463205696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250508084434.1933069-1-cratiu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 May 2025 11:44:34 +0300 you wrote:
> netdev_bind_rx takes ownership of the queue array passed as parameter
> and frees it, so a queue array buffer cannot be reused across multiple
> netdev_bind_rx calls.
>
> This commit fixes that by always passing in a newly created queue array
> to all netdev_bind_rx calls in ncdevmem.
>
> [...]
Here is the summary with links:
- [net,v2] tests/ncdevmem: Fix double-free of queue array
https://git.kernel.org/netdev/net/c/97c4e094a4b2
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-05-09 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 8:44 [PATCH net v2] tests/ncdevmem: Fix double-free of queue array Cosmin Ratiu
2025-05-08 16:23 ` Stanislav Fomichev
2025-05-08 18:31 ` Joe Damato
2025-05-09 7:21 ` Cosmin Ratiu
2025-05-08 20:42 ` Mina Almasry
2025-05-09 7:24 ` Cosmin Ratiu
2025-05-09 23:30 ` 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=174683343176.3841790.11524144387463205696.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).