From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Andrea Mayer <andrea.mayer@uniroma2.it>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
david.lebrun@uclouvain.be, stefano.salsano@uniroma2.it,
paolo.lungaroni@uniroma2.it, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] seg6: separate dst_cache for input and output paths in seg6 lwtunnel
Date: Tue, 31 Mar 2026 18:01:28 +0200 [thread overview]
Message-ID: <ed0d3cd2-0e2d-4bc5-855d-fba079a7db79@6wind.com> (raw)
In-Reply-To: <20260331110755.25042-2-andrea.mayer@uniroma2.it>
Le 31/03/2026 à 13:07, Andrea Mayer a écrit :
> The seg6 lwtunnel uses a single dst_cache per encap route, shared
> between seg6_input_core() and seg6_output_core(). These two paths
> can perform the post-encap SID lookup in different routing contexts
> (e.g., ip rules matching on the ingress interface, or VRF table
> separation). Whichever path runs first populates the cache, and the
> other reuses it blindly, bypassing its own lookup.
>
> Fix this by splitting the cache into cache_input and cache_output,
> so each path maintains its own cached dst independently.
>
> Fixes: 6c8702c60b88 ("ipv6: sr: add support for SRH encapsulation and injection with lwtunnels")
> Cc: stable@vger.kernel.org
> Signed-off-by: Andrea Mayer <andrea.mayer@uniroma2.it>
Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Thanks,
Nicolas
next prev parent reply other threads:[~2026-03-31 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 11:07 [PATCH net 0/2] seg6: fix dst_cache sharing in seg6 lwtunnel Andrea Mayer
2026-03-31 11:07 ` [PATCH net 1/2] seg6: separate dst_cache for input and output paths " Andrea Mayer
2026-03-31 16:01 ` Nicolas Dichtel [this message]
2026-03-31 11:07 ` [PATCH net 2/2] selftests: seg6: add test for dst_cache isolation " Andrea Mayer
2026-03-31 16:15 ` Nicolas Dichtel
2026-04-01 13:03 ` Andrea Mayer
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=ed0d3cd2-0e2d-4bc5-855d-fba079a7db79@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo.lungaroni@uniroma2.it \
--cc=stable@vger.kernel.org \
--cc=stefano.salsano@uniroma2.it \
/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