[linus:master] [selftests] 7e0147592b: kernel-selftests.net.fcnal-test.sh.IPv4_ping.With_VRF.net.ipv4.raw_l3mdev_accept=1.ping_local_device_bind_-_ns-A_IP.fail

Hi David,

Please be noted that we already reported this failure on linux stable
tree at:
https://lore.kernel.org/all/YrLElch6LCYs1MPx@xsang-OptiPlex-9020/ (local)
We noticed this failure still exists on mainline, so we report again FYI.


Greeting,

We noticed kernel-selftests.net.fcnal-test.sh.IPv4_ping.With_VRF.net.ipv4.raw_l3mdev_accept=1.ping_local_device_bind_-_ns-A_IP.fail due to commit (built with gcc-11):

commit: 7e0147592b5c4f9e2eb8c54a7857a56d4863f74e ("selftests: Add duplicate config only for MD5 VRF tests")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linux-next/master 591cd61541b9b95401e17dca24be486e32104cb8]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-2ed09c3b-1_20221128
with following parameters:

	group: net
	test: fcnal-test.sh
	atomic_test: ipv4_ping

test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt

on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 28G memory

caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):


# With VRF
# 
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# 
# TEST: ping out, VRF bind - ns-B IP                                            [ OK ]
# TEST: ping out, device bind - ns-B IP                                         [ OK ]
# TEST: ping out, vrf device + dev address bind - ns-B IP                       [ OK ]
# TEST: ping out, vrf device + vrf address bind - ns-B IP                       [ OK ]
# TEST: ping out, VRF bind - ns-B loopback IP                                   [ OK ]
# TEST: ping out, device bind - ns-B loopback IP                                [ OK ]
# TEST: ping out, vrf device + dev address bind - ns-B loopback IP              [ OK ]
# TEST: ping out, vrf device + vrf address bind - ns-B loopback IP              [ OK ]
# TEST: ping in - ns-A IP                                                       [ OK ]
# TEST: ping in - VRF IP                                                        [ OK ]
# TEST: ping local, VRF bind - ns-A IP                                          [ OK ]
# TEST: ping local, VRF bind - VRF IP                                           [FAIL]
# TEST: ping local, VRF bind - loopback                                         [ OK ]
# TEST: ping local, device bind - ns-A IP                                       [FAIL]  <--
# TEST: ping local, device bind - VRF IP                                        [ OK ]
# TEST: ping local, device bind - loopback                                      [ OK ]
# TEST: ping out, vrf bind, blocked by rule - ns-B loopback IP                  [ OK ]
# TEST: ping out, device bind, blocked by rule - ns-B loopback IP               [ OK ]
# TEST: ping in, blocked by rule - ns-A loopback IP                             [ OK ]
# TEST: ping out, vrf bind, unreachable route - ns-B loopback IP                [ OK ]
# TEST: ping out, device bind, unreachable route - ns-B loopback IP             [ OK ]
# TEST: ping in, unreachable route - ns-A loopback IP                           [ OK ]
# 
# Tests passed:  58
# Tests failed:   2
not ok 1 selftests: net: fcnal-test.sh # exit=1



If you fix the issue, kindly add following tag
| Reported-by: kernel test robot [off-list ref]
| Link: https://lore.kernel.org/oe-lkp/202212091549.db616928-yujie.liu@intel.com (local)


To reproduce:

        git clone https://github.com/intel/lkp-tests.git
        cd lkp-tests
        sudo bin/lkp install job.yaml           # job file is attached in this email
        bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
        sudo bin/lkp run generated-yaml-file

        # if come across any failure that blocks the test,
        # please remove ~/.lkp and /lkp dir to run from a clean state.


-- 
0-DAY CI Kernel Test Service
https://01.org/lkp