Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp2761725ybh; Mon, 5 Aug 2019 06:26:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqwNp6N6V4FbxK4IRC8HWkK27q19dsalDfGGG8G1tcAdL3wbo6q+brnBWhFblmvLwZPMxiBR X-Received: by 2002:a17:90a:6546:: with SMTP id f6mr17983055pjs.11.1565011602785; Mon, 05 Aug 2019 06:26:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565011602; cv=none; d=google.com; s=arc-20160816; b=oxi4f4PHtA8BHKgJ92vGQwjb+xyG6oTad7vCFN/blTz5CxJBwEJh0JZCACh3RONERm p4ddNeUXQWClb3XuvOMBtKyCglPu7fAQW1GKHSp7tFQ/A+Yuea/Hctrh9n9bc0FrHViM QVCekyUQcM85aOtDoadSZIhS4Q8JtLxHKU6OG8gEiWHgl/GIGNxs15R8Xn0F1Ycfe/8w +YE9osTALi40MPrdvdCEJoGRAE8mlq8S+N+TwhfOHKV/tYW8FL3RWwokd5maTXWgtZkB qUyZ02BhkpjT8kY7l/Nns1a8x56mFUENyIaIanCTVPAaVpezY8SRIyZ3TjfBh800utAN eDyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=LNBhVHvxyLYr4uRuLUvPaRm93JbSbobRolLASSyD70Y=; b=bYZ+XR4NobSwTCV/OzoLaTzShHM4No4LRDRyyprqLRwbSxzmHfx9Fl3KbK8gBXO6Hb eF9EqvE/rvRlxGw6XFetv1ZV4Bm85GfNh28cH8ZLIK0LaB2DiAnW+IpcjDelqo4Ek1ZO ig3kG8CVzaw4Wtdzh1nhEdB5ylGrIxVSGDi5Kwew3XE60v9zzps0QssdortuxKVZjCKz BNJTs8eBeq+iuYLXFSsxZzn6uN2oOQTrhKAdeb9h3l6w2/dA8k7airNnLBf9BnjjaR84 eI0RPqDcvFCt8CCsEsknCdc9rlUEiQoc/660GTewVfDqZwTPxRVWSdMvFKenFGvdCN59 O4wg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=niOxGXoo; 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 k33si46667109pgi.563.2019.08.05.06.26.27; Mon, 05 Aug 2019 06:26:42 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=niOxGXoo; 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 S1731312AbfHENZv (ORCPT + 99 others); Mon, 5 Aug 2019 09:25:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:34320 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731288AbfHENZr (ORCPT ); Mon, 5 Aug 2019 09:25:47 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F3F2820651; Mon, 5 Aug 2019 13:25:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565011546; bh=DRDerXr9DW86qLGdmqopt7ynBm6nHUnwaVDipglW7BA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=niOxGXooJz3aBI+grsWaEPpuX7RGxjW2F42uCpcQxzVgcahXqBoRN6Up21UbL1Ro1 Knhwxc/g6tRXWEqupTDSQjrKoIWH1sUqMYYFH2JzCGwSiU+rHPdIkIpINWxGcu1htg dMInEVnim/tNv456FDGlszgPKhyEVp9uu4WTzXLI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Mike Marciniszyn , Kaike Wan , Jason Gunthorpe Subject: [PATCH 5.2 129/131] IB/hfi1: Field not zero-ed when allocating TID flow memory Date: Mon, 5 Aug 2019 15:03:36 +0200 Message-Id: <20190805125000.619598200@linuxfoundation.org> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190805124951.453337465@linuxfoundation.org> References: <20190805124951.453337465@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Kaike Wan commit dc25b239ebeaa3c58e5ceaa732140427d386aa16 upstream. The field flow->resync_npkts is added for TID RDMA WRITE request and zero-ed when a TID RDMA WRITE RESP packet is received by the requester. This field is used to rewind a request during retry in the function hfi1_tid_rdma_restart_req() shared by both TID RDMA WRITE and TID RDMA READ requests. Therefore, when a TID RDMA READ request is retried, this field may not be initialized at all, which causes the retry to start at an incorrect psn, leading to the drop of the retry request by the responder. This patch fixes the problem by zeroing out the field when the flow memory is allocated. Fixes: 838b6fd2d9ca ("IB/hfi1: TID RDMA RcvArray programming and TID allocation") Cc: Link: https://lore.kernel.org/r/20190715164534.74174.6177.stgit@awfm-01.aw.intel.com Reviewed-by: Mike Marciniszyn Signed-off-by: Kaike Wan Signed-off-by: Mike Marciniszyn Signed-off-by: Jason Gunthorpe Signed-off-by: Greg Kroah-Hartman --- drivers/infiniband/hw/hfi1/tid_rdma.c | 1 + 1 file changed, 1 insertion(+) --- a/drivers/infiniband/hw/hfi1/tid_rdma.c +++ b/drivers/infiniband/hw/hfi1/tid_rdma.c @@ -1620,6 +1620,7 @@ static int hfi1_kern_exp_rcv_alloc_flows flows[i].req = req; flows[i].npagesets = 0; flows[i].pagesets[0].mapped = 0; + flows[i].resync_npkts = 0; } req->flows = flows; return 0;