From: David Ahern <dsahern@gmail.com>
To: "Zhou, Jie2X" <jie2x.zhou@intel.com>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Li, ZhijianX" <zhijianx.li@intel.com>,
"Li, Philip" <philip.li@intel.com>,
"Ma, XinjianX" <xinjianx.ma@intel.com>
Subject: Re: [PATCH v2] selftests: net: Correct case name
Date: Sun, 12 Dec 2021 21:09:38 -0700 [thread overview]
Message-ID: <65ca2349-5d11-93fb-d9d3-22ff87fe7533@gmail.com> (raw)
In-Reply-To: <PH0PR11MB47925643B3A60192AAD18D7AC5749@PH0PR11MB4792.namprd11.prod.outlook.com>
On 12/12/21 8:08 PM, Zhou, Jie2X wrote:
> hi,
>
> I try to apply the "selftests: Fix raw socket bind tests with VRF" patch.
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=0f108ae44520
>
> And found that following changes.
> TEST: Raw socket bind to local address - ns-A IP [ OK ]
> => TEST: Raw socket bind to local address - ns-A IP [FAIL]
> TEST: Raw socket bind to local address - VRF IP [FAIL]
> => TEST: Raw socket bind to local address - VRF IP [ OK ]
>
After the last round of patches all tests but 2 pass with the 5.16.0-rc3
kernel (net-next based) and ubuntu 20.04 OS.
The 2 failures are due local pings and to bugs in 'ping' - it removes
the device bind by calling setsockopt with an "" arg.
next prev parent reply other threads:[~2021-12-13 4:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 2:28 [PATCH v2] selftests: net: Correct case name Li Zhijian
2021-12-02 12:20 ` patchwork-bot+netdevbpf
2021-12-07 6:05 ` lizhijian
2021-12-08 3:01 ` David Ahern
2021-12-08 3:28 ` lizhijian
2021-12-08 3:14 ` David Ahern
2021-12-08 3:38 ` lizhijian
2021-12-08 4:07 ` David Ahern
2021-12-13 3:08 ` Zhou, Jie2X
2021-12-13 4:09 ` David Ahern [this message]
2021-12-13 9:44 ` Zhou, Jie2X
2021-12-13 15:58 ` David Ahern
2021-12-15 1:36 ` Zhou, Jie2X
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=65ca2349-5d11-93fb-d9d3-22ff87fe7533@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=jie2x.zhou@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=shuah@kernel.org \
--cc=xinjianx.ma@intel.com \
--cc=zhijianx.li@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.