From: patchwork-bot+netdevbpf@kernel.org
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
hkelam@marvell.com, sbhatta@marvell.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify
Date: Mon, 25 May 2026 20:00:07 +0000 [thread overview]
Message-ID: <177973920715.3098866.6475333748941191821.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260520154157.1439319-1-michael.bommarito@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 11:41:57 -0400 you wrote:
> rvu_mbox_handler_rep_event_notify() in drivers/net/ethernet/marvell/
> octeontx2/af/rvu_rep.c queues a sender-controlled REP_EVENT_NOTIFY
> request body verbatim, and rvu_rep_up_notify() then forwards
> event->pcifunc (the nested body field, distinct from the
> AF-normalised header pcifunc) into rvu_get_pfvf(), rvu_get_pf() and
> the AF->PF mailbox device index without any bounds check.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify
https://git.kernel.org/netdev/net/c/2156a29aecff
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-05-25 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 15:41 [PATCH net] octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify Michael Bommarito
2026-05-25 20: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=177973920715.3098866.6475333748941191821.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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