The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "luwei (O)" <luwei32@huawei.com>
To: David Ahern <dsahern@kernel.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] ipv6: Add lwtunnel encap size of all siblings in nexthop calculation
Date: Wed, 15 Feb 2023 14:28:18 +0800	[thread overview]
Message-ID: <0fa82f21-015a-c89f-c837-18df04c3965d@huawei.com> (raw)
In-Reply-To: <32817680-56e6-594c-2acb-0022e4e8548e@kernel.org>

ok, I will send v2 version

在 2023/2/14 11:45 PM, David Ahern 写道:
> On 2/14/23 2:29 AM, Lu Wei wrote:
>> In function rt6_nlmsg_size(), the length of nexthop is calculated
>> by multipling the nexthop length of fib6_info and the number of
>> siblings. However if the fib6_info has no lwtunnel but the siblings
>> have lwtunnels, the nexthop length is less than it should be, and
>> it will trigger a warning in inet6_rt_notify() as follows:
>>
>> WARNING: CPU: 0 PID: 6082 at net/ipv6/route.c:6180 inet6_rt_notify+0x120/0x130
>> ......
>> Call Trace:
>>   <TASK>
>>   fib6_add_rt2node+0x685/0xa30
>>   fib6_add+0x96/0x1b0
>>   ip6_route_add+0x50/0xd0
>>   inet6_rtm_newroute+0x97/0xa0
>>   rtnetlink_rcv_msg+0x156/0x3d0
>>   netlink_rcv_skb+0x5a/0x110
>>   netlink_unicast+0x246/0x350
>>   netlink_sendmsg+0x250/0x4c0
>>   sock_sendmsg+0x66/0x70
>>   ___sys_sendmsg+0x7c/0xd0
>>   __sys_sendmsg+0x5d/0xb0
>>   do_syscall_64+0x3f/0x90
>>   entry_SYSCALL_64_after_hwframe+0x72/0xdc
>>
>> This bug can be reproduced by script:
>>
>> ip -6 addr add 2002::2/64 dev ens2
>> ip -6 route add 100::/64 via 2002::1 dev ens2 metric 100
>>
>> for i in 10 20 30 40 50 60 70;
>> do
>> 	ip link add link ens2 name ipv_$i type ipvlan
>> 	ip -6 addr add 2002::$i/64 dev ipv_$i
>> 	ifconfig ipv_$i up
>> done
>>
>> for i in 10 20 30 40 50 60;
>> do
>> 	ip -6 route append 100::/64 encap ip6 dst 2002::$i via 2002::1
>> dev ipv_$i metric 100
>> done
>>
>> ip -6 route append 100::/64 via 2002::1 dev ipv_70 metric 100
> would be good to add that test to
>     tools/testing/selftests/net/fib_tests.sh
>
> along with a similar one for IPv4.
>
>> This patch fixes it by adding nexthop_len of every siblings using
>> rt6_nh_nlmsg_size().
>>
>> Fixes: beb1afac518d ("net: ipv6: Add support to dump multipath routes via RTA_MULTIPATH attribute")
>> Signed-off-by: Lu Wei <luwei32@huawei.com>
>> ---
>>   net/ipv6/route.c | 11 ++++++-----
>>   1 file changed, 6 insertions(+), 5 deletions(-)
>>
> Reviewed-by: David Ahern <dsahern@kernel.org>
>
>
> .

-- 
Best Regards,
Lu Wei


  reply	other threads:[~2023-02-15  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  9:29 [PATCH net] ipv6: Add lwtunnel encap size of all siblings in nexthop calculation Lu Wei
2023-02-14 15:45 ` David Ahern
2023-02-15  6:28   ` luwei (O) [this message]
2023-02-14 17:39 ` Alexander Lobakin
2023-02-14 18:11   ` David Ahern
2023-02-15 15:58     ` Alexander Lobakin

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=0fa82f21-015a-c89f-c837-18df04c3965d@huawei.com \
    --to=luwei32@huawei.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox