From: Lu Wei <luwei32@huawei.com>
To: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH net,v3,0/2] Fix a fib6 info notification bug
Date: Wed, 22 Feb 2023 12:20:49 +0800 [thread overview]
Message-ID: <20230222042051.325307-1-luwei32@huawei.com> (raw)
This patch set fixes a length calculation bug in fib6 info notification
and adds two testcases.
The test reult is listed as follows:
before the fix patch:
Fib6 info length calculation in route notify test
TEST: ipv6 route add notify [FAIL]
Fib4 info length calculation in route notify test
TEST: ipv4 route add notify [ OK ]
after the fix patch:
Fib6 info length calculation in route notify test
TEST: ipv6 route add notify [ OK ]
Fib4 info length calculation in route notify test
TEST: ipv4 route add notify [ OK ]
Lu Wei (2):
ipv6: Add lwtunnel encap size of all siblings in nexthop calculation
selftests: fib_tests: Add test cases for IPv4/IPv6 in route notify
net/ipv6/route.c | 11 +--
tools/testing/selftests/net/fib_tests.sh | 97 +++++++++++++++++++++++-
2 files changed, 102 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2023-02-22 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 4:20 Lu Wei [this message]
2023-02-22 4:20 ` [PATCH net,v3,1/2] ipv6: Add lwtunnel encap size of all siblings in nexthop calculation Lu Wei
2023-02-22 4:20 ` [PATCH net,v3,2/2] selftests: fib_tests: Add test cases for IPv4/IPv6 in route notify Lu Wei
2023-02-22 3:20 ` David Ahern
2023-02-22 6:46 ` luwei (O)
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=20230222042051.325307-1-luwei32@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