All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Fourie Zhang <littleddfu@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, jbenc@redhat.com,
	horms@kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, aconole@redhat.com, i.maximets@ovn.org,
	dev@openvswitch.org, stable@vger.kernel.org, corvus@tencent.com,
	fouriezhang@tencent.com
Subject: Re: [PATCH net v2] net: mpls: clear inner_protocol when the last label is popped
Date: Fri, 04 Sep 2026 23:10:09 +0000	[thread overview]
Message-ID: <178856340990.1009860.14708368396891138023.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902092719.2874481-1-fouriezhang@tencent.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  2 Sep 2026 17:27:12 +0800 you wrote:
> skb_mpls_push() records the pre-encapsulation network header once, gated
> on !skb->inner_protocol. skb_mpls_pop() never clears that record, so it
> outlives the encapsulation it describes.
> 
> Open vSwitch can then re-push MPLS onto a packet whose
> inner_network_header still points at the older, deeper offset: push a
> label, pop every label, recirculate (ovs_flow_key_update() re-derives
> key->eth.type and resets network_header, but leaves inner_*), then push
> again. ovs_fragment() trusts the record:
> 
> [...]

Here is the summary with links:
  - [net,v2] net: mpls: clear inner_protocol when the last label is popped
    https://git.kernel.org/netdev/net/c/78a86d75a70e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-04 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  9:27 [PATCH net v2] net: mpls: clear inner_protocol when the last label is popped Fourie Zhang
2026-09-03 11:17 ` Jiri Benc
2026-09-04 23:10 ` 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=178856340990.1009860.14708368396891138023.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aconole@redhat.com \
    --cc=corvus@tencent.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=edumazet@google.com \
    --cc=fouriezhang@tencent.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=jbenc@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=littleddfu@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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.