From: Hangbin Liu <liuhangbin@gmail.com>
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, shannon.nelson@oracle.com,
weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net] selftests: rtnetlink: correct xfrm policy rule in kci_test_ipsec_offload
Date: Fri, 2 Dec 2022 10:06:56 +0800 [thread overview]
Message-ID: <Y4ldwIQlcXyZek1A@Laptop-X1> (raw)
In-Reply-To: <20221201082246.14131-1-shaozhengchao@huawei.com>
On Thu, Dec 01, 2022 at 04:22:46PM +0800, Zhengchao Shao wrote:
> When testing in kci_test_ipsec_offload, srcip is configured as $dstip,
> it should add xfrm policy rule in instead of out.
> The test result of this patch is as follows:
> PASS: ipsec_offload
>
> Fixes: 2766a11161cc ("selftests: rtnetlink: add ipsec offload API test")
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>
> ---
> tools/testing/selftests/net/rtnetlink.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/rtnetlink.sh b/tools/testing/selftests/net/rtnetlink.sh
> index 0900c5438fbb..275491be3da2 100755
> --- a/tools/testing/selftests/net/rtnetlink.sh
> +++ b/tools/testing/selftests/net/rtnetlink.sh
> @@ -782,7 +782,7 @@ kci_test_ipsec_offload()
> tmpl proto esp src $srcip dst $dstip spi 9 \
> mode transport reqid 42
> check_err $?
> - ip x p add dir out src $dstip/24 dst $srcip/24 \
> + ip x p add dir in src $dstip/24 dst $srcip/24 \
> tmpl proto esp src $dstip dst $srcip spi 9 \
> mode transport reqid 42
> check_err $?
> --
> 2.34.1
>
Acked-by: Hangbin Liu <liuhangbin@gmail.com>
next prev parent reply other threads:[~2022-12-02 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 8:22 [PATCH net] selftests: rtnetlink: correct xfrm policy rule in kci_test_ipsec_offload Zhengchao Shao
2022-12-02 2:06 ` Hangbin Liu [this message]
2022-12-03 5:30 ` patchwork-bot+netdevbpf
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=Y4ldwIQlcXyZek1A@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@oracle.com \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@huawei.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