Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2990856imu; Sun, 9 Dec 2018 14:28:47 -0800 (PST) X-Google-Smtp-Source: AFSGD/X28JSMpZjPZSAFjhZm3m5KkIavT+2XPZnFEal0cTlMPSU02auS63mIUe9QLe+oCvVtD8n2 X-Received: by 2002:aa7:8286:: with SMTP id s6mr9901586pfm.63.1544394527613; Sun, 09 Dec 2018 14:28:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544394527; cv=none; d=google.com; s=arc-20160816; b=BN0lqEkXlxJ0CyrWYRMgTj2ZfKdatGDCM1m82PTw8gB26tE+/Wn0+hlqfDJs50lmVN ailgYiyDvobL70jp52/szvWSNpNEUkJkhez3vGjjNIfbmyqKpQavqCq5IVVku1LJhmsw jAVEZ2Z2o+nOfra5Ggynmw7y2Z381O/dPZODaW1CBbOBJ9e6ziOoh1GemPhq1yml8LDm bnI3OquO6opZEWk5EVss0ub14z4O3OHFLwd1Rhgg1VY9hZT9RDg5Jtnc7xFh77fU7ewT imH7vFBKdCFmwN7ptmTk71S6kMx4BAIl8REH3hDK9tVP7B7dSyaHsQ++5rFynztJgQ4d ANpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=JuZt8ZV73TpGbnRlnE95ZT2un/mMmdGlZy166+hgkEs=; b=PTZq3pIXFBVzTxxCAMwE2IFS0gIh8/AjHwpOQI+FnMwZbDqfJaSgeCyR1xHrQAsR8+ 6jg1I4HVVJCggbVy4sWup2zUPxlLl6eFBnws5yZq3hneKHe7/rchcEsgyS6aD+N4i7sc nfh2AMA5WZTYSvMAEM2tGS9+3GfLupuS+mw9xl+7aURuMIrqc0aERmUSxOQFTffLYwEx l5oT+Cg/jzsTaC6d8kyQEn+y0q9lKJq4/MJWhm72Fqyf6J/FSVbMJYgRU2qlP90KtkI8 1cdsJi8FRD7wGr39pZyM3QXwjlYojRJ1Jpc626CV+HbSqyVyafplz5VChsfUhKjwSSCS cW0g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v11si8443833pgo.11.2018.12.09.14.28.32; Sun, 09 Dec 2018 14:28:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728477AbeLIWZ5 (ORCPT + 99 others); Sun, 9 Dec 2018 17:25:57 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:34858 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726436AbeLIVzP (ORCPT ); Sun, 9 Dec 2018 16:55:15 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW72e-0002ir-GT; Sun, 09 Dec 2018 21:55:12 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72b-0003Ki-Jv; Sun, 09 Dec 2018 21:55:09 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Jason Gunthorpe" , "Leon Romanovsky" , "Denis Drozdov" , "Feras Daoud" , "Erez Shitrit" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 094/328] IB/IPoIB: Set ah valid flag in multicast send flow In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Denis Drozdov commit 75da96067ade4e7854379ec2f7834f3497652b1a upstream. The change of ipoib_ah data structure with adding "valid" flag and checks of ah->valid in ipoib_start_xmit affected multicast packet flow. Since the multicast flow doesn't invoke path_rec_start, "ah->valid" flag remains unset, so that ipoib_start_xmit end up with neigh_refresh_path instead of sending the packet using neigh. "ah->valid" has to be set in multicast send flow. As a result IPoIB starts sending packets via neigh immediately and eliminates 60sec delay of neigh keep alive interval. The typical example of this issue are two sequential arpings: arping 11.134.208.9 -> got response (mcast_send) arping 11.134.208.9 -> no response (ah->valid = 0) Fixes: fa9391dbad4b ("RDMA/ipoib: Update paths on CLIENT_REREG/SM_CHANGE events") Signed-off-by: Denis Drozdov Reviewed-by: Erez Shitrit Reviewed-by: Feras Daoud Signed-off-by: Leon Romanovsky Signed-off-by: Jason Gunthorpe Signed-off-by: Ben Hutchings --- drivers/infiniband/ulp/ipoib/ipoib_multicast.c | 1 + 1 file changed, 1 insertion(+) --- a/drivers/infiniband/ulp/ipoib/ipoib_multicast.c +++ b/drivers/infiniband/ulp/ipoib/ipoib_multicast.c @@ -734,6 +734,7 @@ out: if (neigh && list_empty(&neigh->list)) { kref_get(&mcast->ah->ref); neigh->ah = mcast->ah; + neigh->ah->valid = 1; list_add_tail(&neigh->list, &mcast->neigh_list); } }