From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, vladimir.oltean@nxp.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: mscc: ocelot: validate netdev belongs to switch in .netdev_to_port()
Date: Wed, 10 Jun 2026 01:00:18 +0000 [thread overview]
Message-ID: <178105321863.2773882.14974731560626407551.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260606125247.305167-1-mmyangfl@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 6 Jun 2026 20:52:44 +0800 you wrote:
> The .netdev_to_port() currently takes only a net_device and returns the
> port index, without verifying the netdev actually belongs to the switch
> being operated on. This can cause flower rule parsing to silently
> resolve to a wrong port on the local hardware.
>
> Update both implementations felix_netdev_to_port() and
> ocelot_netdev_to_port() to validate ownership. Also update the callers
> in ocelot_flower.c to pass through the ocelot context.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: mscc: ocelot: validate netdev belongs to switch in .netdev_to_port()
https://git.kernel.org/netdev/net-next/c/ea07514700f7
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-06-10 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 12:52 [PATCH net-next v2] net: mscc: ocelot: validate netdev belongs to switch in .netdev_to_port() David Yang
2026-06-10 1: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=178105321863.2773882.14974731560626407551.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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