From: patchwork-bot+netdevbpf@kernel.org
To: Narcisa Vasile <narcisav.kernel@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, daniel.zahka@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, willemb@google.com,
petrm@nvidia.com, anubhavsinggh@google.com,
richardbgobert@gmail.com, lixiaoyan@google.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: gro: fix OOB access when under-coalescing
Date: Thu, 17 Sep 2026 02:20:17 +0000 [thread overview]
Message-ID: <178961161737.3379718.8594184186847332667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916010029.50911-1-narcisav.kernel@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Sep 2026 18:00:29 -0700 you wrote:
> When more packets than expected are received, num_pkt
> could index beyond the end of the array. Add a check to prevent
> OOB access.
>
> Continue receiving until the FIN is received to obtain
> the total packet count. This helps diagnose issues by
> distinguishing the cases where no coalescing happened from
> the partial-coalescing cases that didn't meet the test check.
>
> [...]
Here is the summary with links:
- [net] selftests: net: gro: fix OOB access when under-coalescing
https://git.kernel.org/netdev/net-next/c/7bc21b740291
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:[~2026-09-17 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 1:00 [PATCH net] selftests: net: gro: fix OOB access when under-coalescing Narcisa Vasile
2026-09-17 2:20 ` 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=178961161737.3379718.8594184186847332667.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anubhavsinggh@google.com \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=narcisav.kernel@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=richardbgobert@gmail.com \
--cc=shuah@kernel.org \
--cc=willemb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.