From: Simon Horman <horms@kernel.org>
To: David Bauer <mail@david-bauer.net>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
James Chapman <jchapman@katalix.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH net] net l2tp: drop flow hash on forward
Date: Fri, 26 Apr 2024 10:58:41 +0100 [thread overview]
Message-ID: <20240426095841.GE42092@kernel.org> (raw)
In-Reply-To: <20240424171110.13701-1-mail@david-bauer.net>
+ Randy Dunlap
On Wed, Apr 24, 2024 at 07:11:10PM +0200, David Bauer wrote:
> Drop the flow-hash of the skb when forwarding to the L2TP netdev.
>
> This avoids the L2TP qdisc from using the flow-hash from the outer
> packet, which is identical for every flow within the tunnel.
>
> This does not affect every platform but is specific for the ethernet
> driver. It depends on the platform including L4 information in the
> flow-hash.
>
> One such example is the Mediatek Filogic MT798x family of networking
> processors.
>
> Fixes: d9e31d17ceba ("l2tp: Add L2TP ethernet pseudowire support")
> Acked-by: James Chapman <jchapman@katalix.com>
> Signed-off-by: David Bauer <mail@david-bauer.net>
Reviewed-by: Simon Horman <horms@kernel.org>
> ---
> net/l2tp/l2tp_eth.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/l2tp/l2tp_eth.c b/net/l2tp/l2tp_eth.c
> index 39e487ccc468..8ba00ad433c2 100644
> --- a/net/l2tp/l2tp_eth.c
> +++ b/net/l2tp/l2tp_eth.c
> @@ -127,6 +127,9 @@ static void l2tp_eth_dev_recv(struct l2tp_session *session, struct sk_buff *skb,
> /* checksums verified by L2TP */
> skb->ip_summed = CHECKSUM_NONE;
>
> + /* drop outer flow-hash */
> + skb_clear_hash(skb);
> +
> skb_dst_drop(skb);
> nf_reset_ct(skb);
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-04-26 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:11 [PATCH net] net l2tp: drop flow hash on forward David Bauer
2024-04-26 9:58 ` Simon Horman [this message]
2024-04-26 12:00 ` patchwork-bot+netdevbpf
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=20240426095841.GE42092@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=mail@david-bauer.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
/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).