Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp722796pxb; Thu, 21 Oct 2021 08:16:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzpq4MsEZ4SmMKAFY170iqBr9OpZ25W4W07akAsq4dkiE9HS/+1br3vzgZWIc9VqCPCTXLg X-Received: by 2002:a17:902:7fcf:b0:13e:c994:ee67 with SMTP id t15-20020a1709027fcf00b0013ec994ee67mr5762037plb.12.1634829415328; Thu, 21 Oct 2021 08:16:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634829415; cv=none; d=google.com; s=arc-20160816; b=JkvCica8jyE0gt+3UYWqEQjkJAPz/g6NgINnrs78iBCt0/ZIYR0Nbmt4m1qQJDJ9a2 /qpHD2k43ymMFXG6//qN+OPKZwYkVkiaNY8ykGo2jDQpnoow6yc8R6mX8P7M1wCC4lGv p8wH3pAtkJCJGWYFgnAKsM6zq09oZeds9u3f2fWMq9wAxjM5ivUboI46MvVTQkLZM0lL PUNm54PMr4ncxzPjd8KB68/GdRH/1HoJEP0alZJMShv6xWIfWs8ya3KBoSceGtUcc3tx p/km748KdGgQ60qkA1Mvqj1cz2H9VkBbXOs1Ic10IJCLpNPu8II8UD/AkuyMAn0IvRt8 yaig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=jF1v7J2qtt73Uo1UTn9Y2oZJT8/iM1SgahZXbvXSNO0=; b=egsnO5ba1R+h1ccpjdPWuC+Pfa9JONNGv0Xv+KniWlzJ9r3Hy2pSvzSnG3NEQiYP1C NYgKZGQl9OqSotkf2apViUDi2iWjkuYSweHynQtNbMJCeBRzDO1YEHAKM0FSJbJsZ++S wimvF9z/1fD8+qZAZ62BPLTnd7CSgH/uVfU7I5y/57DlyeVGWcrcYsv67ycqfGQngHH8 O/MlAoUWc/PVeAvDMwC5lCWyWbAR2Rp8TcolF9I6WkH2syyvC1mvd8pnOXkOfZsAhAUs 7OBmAE+phuUefDoBaRzaYh8cHX+lFv6be+hnNtJSHb7MtNEBx6QB+sdzWKCEjfFphdfE r3ag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d10si8124975plr.295.2021.10.21.08.16.40; Thu, 21 Oct 2021 08:16:55 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232088AbhJUPR6 (ORCPT + 99 others); Thu, 21 Oct 2021 11:17:58 -0400 Received: from mga02.intel.com ([134.134.136.20]:40075 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232125AbhJUPRk (ORCPT ); Thu, 21 Oct 2021 11:17:40 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10144"; a="216224942" X-IronPort-AV: E=Sophos;i="5.87,170,1631602800"; d="scan'208";a="216224942" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Oct 2021 08:14:32 -0700 X-IronPort-AV: E=Sophos;i="5.87,170,1631602800"; d="scan'208";a="444837642" Received: from xsang-optiplex-9020.sh.intel.com (HELO xsang-OptiPlex-9020) ([10.239.159.41]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Oct 2021 08:14:29 -0700 Date: Thu, 21 Oct 2021 23:34:21 +0800 From: Oliver Sang To: Paolo Abeni Cc: "David S. Miller" , LKML , lkp@lists.01.org, lkp@intel.com, mptcp@lists.01.org Subject: Re: [veth] 9d3684c24a: kernel-selftests.net/mptcp.mptcp_join.sh.fail Message-ID: <20211021153421.GD16330@xsang-OptiPlex-9020> References: <20210907142758.GD17617@xsang-OptiPlex-9020> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Paolo Abeni, On Tue, Sep 07, 2021 at 04:35:47PM +0200, Paolo Abeni wrote: > 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. sorry for late. we tested it again, right, what we captured is just above failure. now we found by more runs, we could also reproduce on parent, though the rate is very low. at the same time, always fail on this commit. 4752eeb3d891c279 9d3684c24a5232c2d7ea8f8a3e6 ---------------- --------------------------- fail:runs %reproduction fail:runs | | | 1:8 100% 9:10 kernel-selftests.net/mptcp.mptcp_join.sh.fail 7:8 -88% :10 kernel-selftests.net/mptcp.mptcp_join.sh.pass anyway, since reproduced on parent, this seems a false positive. sorry for inconvenience. > > Cheers, > > Paolo >