[LTP] TI-RPC test failures; network configuration related?

[Chuck Lever III]

For a while now my nightly "runltp -f net.tirpc_tests" have
thrown a bunch of failures but I haven't had time to look
into it until now. Without modification, about half of the
client test programs segfault.

Here's a sample test failure. I instrumented the
tirpc_clnt_destroy test case and the rpc_tests.sh script as
shown below, but I still don't understand why clnt_create(3t)
is failing.

Seems to occur on all recent versions of Fedora with stock
kernels or custom-built kernels.


[root@cel-tirpc ltp]# testcases/bin/rpc_test.sh -s tirpc_svc_2 -c tirpc_clnt_destroy
rpc_test 1 TINFO: Running: rpc_test.sh -s tirpc_svc_2 -c tirpc_clnt_destroy
rpc_test 1 TINFO: initialize 'lhost' 'ltp_ns_veth2' interface
rpc_test 1 TINFO: add local addr 10.0.0.2/24
rpc_test 1 TINFO: add local addr fd00:1:1:1::2/64
rpc_test 1 TINFO: initialize 'rhost' 'ltp_ns_veth1' interface
rpc_test 1 TINFO: add remote addr 10.0.0.1/24
rpc_test 1 TINFO: add remote addr fd00:1:1:1::1/64
rpc_test 1 TINFO: Network config (local -- remote):
rpc_test 1 TINFO: ltp_ns_veth2 -- ltp_ns_veth1
rpc_test 1 TINFO: 10.0.0.2/24 -- 10.0.0.1/24
rpc_test 1 TINFO: fd00:1:1:1::2/64 -- fd00:1:1:1::1/64
rpc_test 1 TINFO: timeout per run is 0h 5m 0s
rpc_test 1 TINFO: check registered RPC with rpcinfo
rpc_test 1 TINFO: registered RPC:
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  46925  status
    100024    1   tcp  60195  status
    100005    1   udp  20048  mountd
    100005    1   tcp  20048  mountd
    100005    2   udp  20048  mountd
    100005    2   tcp  20048  mountd
    100005    3   udp  20048  mountd
    100005    3   tcp  20048  mountd
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049  nfs_acl
    100003    3   udp   2049  nfs
    100227    3   udp   2049  nfs_acl
    100021    1   udp  33304  nlockmgr
    100021    3   udp  33304  nlockmgr
    100021    4   udp  33304  nlockmgr
    100021    1   tcp  42895  nlockmgr
    100021    3   tcp  42895  nlockmgr
    100021    4   tcp  42895  nlockmgr
        10    1   udp  59751

# Note above: the test RPC program (536875000) does not
# appear in the rpcinfo output. That makes me suspect
# the network namespace configuration on this guest is
# somehow incorrect.

rpc_test 1 TINFO: using libtirpc: yes
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
 1  cel-tirpc (10.0.0.2)  0.501 ms  0.438 ms  0.392 ms
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.122.1   0.0.0.0         UG        0 0          0 enp1s0
10.0.0.0        0.0.0.0         255.255.255.0   U         0 0          0 ltp_ns_veth2
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 enp1s0
rpc_test 1 TFAIL: tirpc_clnt_destroy 10.0.0.2 536875000 failed unexpectedly

# I changed tirpc_clnt_destroy to display the following
# information instead of segfaulting. clnt_create()
# returns NULL and sets the library's rpc_createerr.

rpc_createerr.cf_stat=12
error: No route to host
2
rpc_test 2 TINFO: SELinux enabled in enforcing mode, this may affect test results
rpc_test 2 TINFO: it can be disabled with TST_DISABLE_SELINUX=1 (requires super/root)
rpc_test 2 TINFO: install seinfo to find used SELinux profiles
rpc_test 2 TINFO: loaded SELinux profiles: none

Summary:
passed   0
failed   1
broken   0
skipped  0
warnings 0

--
Chuck Lever