From: patchwork-bot+netdevbpf@kernel•org
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
andrew@lunn•ch, vivien.didelot@gmail•com, f.fainelli@gmail•com,
claudiu.manoil@nxp•com, alexandre.belloni@bootlin•com,
UNGLinuxDriver@microchip•com
Subject: Re: [PATCH net] net: mscc: ocelot: fix all IP traffic getting trapped to CPU with PTP over IP
Date: Sat, 05 Feb 2022 15:30:08 +0000 [thread overview]
Message-ID: <164407500845.24838.2078251443580915520.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220204230321.3779706-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Sat, 5 Feb 2022 01:03:21 +0200 you wrote:
> The filters for the PTP trap keys are incorrectly configured, in the
> sense that is2_entry_set() only looks at trap->key.ipv4.dport or
> trap->key.ipv6.dport if trap->key.ipv4.proto or trap->key.ipv6.proto is
> set to IPPROTO_TCP or IPPROTO_UDP.
>
> But we don't do that, so is2_entry_set() goes through the "else" branch
> of the IP protocol check, and ends up installing a rule for "Any IP
> protocol match" (because msk is also 0). The UDP port is ignored.
>
> [...]
Here is the summary with links:
- [net] net: mscc: ocelot: fix all IP traffic getting trapped to CPU with PTP over IP
https://git.kernel.org/netdev/net/c/59085208e4a2
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:[~2022-02-05 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 23:03 [PATCH net] net: mscc: ocelot: fix all IP traffic getting trapped to CPU with PTP over IP Vladimir Oltean
2022-02-05 15: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=164407500845.24838.2078251443580915520.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vivien.didelot@gmail$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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