From: Andrea Mayer <andrea.mayer@uniroma2.it>
To: Anton Makarov <am@3a-alliance.com>
Cc: David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
david.lebrun@uclouvain.be, regressions@lists.linux.dev,
stable@vger.kernel.org,
Stefano Salsano <stefano.salsano@uniroma2.it>,
Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
Ahmed Abdelsalam <ahabdels.dev@gmail.com>,
Andrea Mayer <andrea.mayer@uniroma2.it>
Subject: Re: [REGRESSION] net: SRv6 End.DT6 function is broken in VRF mode
Date: Mon, 6 Jun 2022 14:33:38 +0200 [thread overview]
Message-ID: <20220606143338.91df592bbb7dc2f7db4747e6@uniroma2.it> (raw)
In-Reply-To: <7e315ff1-e172-16c3-44b5-0c83c4c92779@3a-alliance.com>
On Fri, 3 Jun 2022 15:23:26 +0300
Anton Makarov <am@3a-alliance.com> wrote:
> #regzbot introduced: b9132c32e01976686efa26252cc246944a0d2cab
>
> Hi All!
>
> Seems there is a regression of SRv6 End.DT6 function in VRF mode. In the
> following scenario packet is decapsulated successfully on vrf10
> interface but not forwarded to vrf10's slave interface:
>
> ip netns exec r4 ip -6 nexthop add id 1004 encap seg6local action
> End.DT6 vrftable 10 dev vrf10
>
> ip netns exec r4 ip -6 route add fcff:0:4:200:: nhid 1004
>
>
> In End.DT6 legacy mode everything works good:
>
> ip netns exec r4 ip -6 nexthop add id 1004 encap seg6local action
> End.DT6 table 10 dev vrf10
>
> ip netns exec r4 ip -6 route add fcff:0:4:200:: nhid 1004
>
>
> The issue impacts even stable v5.18.1. Please help to fix it.
>
>
> Thanks!
>
> Anton
>
>
>
Hi Anton,
thank you for reporting this issue. I am already working on a fix patch which I
will send shortly.
Andrea
next prev parent reply other threads:[~2022-06-06 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 12:23 [REGRESSION] net: SRv6 End.DT6 function is broken in VRF mode Anton Makarov
2022-06-06 12:33 ` Andrea Mayer [this message]
2022-06-20 4:50 ` Thorsten Leemhuis
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=20220606143338.91df592bbb7dc2f7db4747e6@uniroma2.it \
--to=andrea.mayer@uniroma2.it \
--cc=ahabdels.dev@gmail.com \
--cc=am@3a-alliance.com \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@uniroma2.it \
--cc=regressions@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).