linux-kernel - Re: [veth] 9d3684c24a: kernel-selftests.net/mptcp.mptcp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ade152d7877b21adfd3b9680d729c185ef701bb9.camel@redhat.com>
Date:   Tue, 07 Sep 2021 16:35:47 +0200
From:   Paolo Abeni <pabeni@...hat.com>
To:     kernel test robot <oliver.sang@...el.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
        lkp@...el.com, mptcp@...ts.01.org
Subject: Re: [veth]  9d3684c24a:
 kernel-selftests.net/mptcp.mptcp_join.sh.fail

Hello,

On Tue, 2021-09-07 at 22:27 +0800, kernel test robot wrote:
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):

It's not entirelly clear to me which are the relevant "changes" ???

[...]

> # 36 add multiple addresses IPv6          syn[ ok ] - synack[ ok ] - ack[ ok ]
> #                                         add[ ok ] - echo  [fail] got 1 ADD_ADDR echo[s] expected 2
> # 
> # Server ns stats
> # MPTcpExtMPCapableSYNRX          1                  0.0
> # MPTcpExtMPCapableACKRX          1                  0.0
> # MPTcpExtMPJoinSynRx             2                  0.0
> # MPTcpExtMPJoinAckRx             2                  0.0
> # MPTcpExtEchoAdd                 1                  0.0
> # Client ns stats
> # MPTcpExtMPCapableSYNTX          1                  0.0
> # MPTcpExtMPCapableSYNACKRX       1                  0.0
> # MPTcpExtMPJoinSynAckRx          2                  0.0
> # MPTcpExtAddAddr                 2                  0.0

is the referred change is the above self-test failure?

I belive this is unrelated to the mentioned commit (which behave as no-
op in this scenario). We are working to make our self-tests as stable
as possible, but there are still some sporadic failures. 

I could not reproduce this failure locally.

Cheers,

Paolo