Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <ade152d7877b21adfd3b9680d729c185ef701bb9.camel@redhat.com>
Subject: Re: [veth]  9d3684c24a:
 kernel-selftests.net/mptcp.mptcp_join.sh.fail
From:   Paolo Abeni <pabeni@redhat.com>
To:     kernel test robot <oliver.sang@intel.com>
Cc:     "David S. Miller" <davem@davemloft.net>,
        LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org,
        lkp@intel.com, mptcp@lists.01.org
Date:   Tue, 07 Sep 2021 16:35:47 +0200
In-Reply-To: <20210907142758.GD17617@xsang-OptiPlex-9020>
References: <20210907142758.GD17617@xsang-OptiPlex-9020>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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