Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1326630imu; Tue, 11 Dec 2018 17:33:03 -0800 (PST) X-Google-Smtp-Source: AFSGD/XttJk9JjCMA9qtsEHNFInimQ46xwI7XFXFzQhzaT+wBJmjpQmL1Ib1ZMGakH4SBl020ktP X-Received: by 2002:aa7:8354:: with SMTP id z20mr18152701pfm.81.1544578383815; Tue, 11 Dec 2018 17:33:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544578383; cv=none; d=google.com; s=arc-20160816; b=08a/tAU7qhponBoZZGc50711VauhcVmN+sQyKiaqS3TS6v8DityWoaM+1FrrJ1iEEt azyyme/WBeYkIl4MYcxudA53FdFNECOPsXiNz8uuwje2WgEvczc84lMNTRSlQoLr7E4e 2ltt5a1LpCQI3kGK0PmS8iDDjNcYGG8A2tGH73YnxjCUwAUmtJM8V8yWanquzslWfqbw 7+XosjtzOBiumVxOUsagD5gmtI8JhrwOYjNjNkpviSlpJ4oT+T670pkZz5UHfcc6PsEw NwW3YYQNelfb3py0yO7ifgT3iZBGVhdM6U34YUIA5vel2Fhdun+cfm/cRoig4JtzqyhT k+7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=J6fFGJHnjceq1r5h/KuGidS1/t2IUyPSho208krEb6M=; b=ULvneXCXlqEU5GSfapd+JfD6dx5w0vYiA8DbLN0g87U/BX8t3nF+yeZxOpZkEH2f0p r6r0tfqQCauySNIw8vMjTvJuNn33+P26SIvOggjxKgfrFmCN1rsYLJDPsSDxPkEF/btd pY8aBBYrTKlfmxwkTqYGjxaDk6gNdNO0RpdZ0va6+S4jiGhwa4mu7cmlegTsxNZWCPqn UI68587hckvDxh3CydPcRUJglTHhsyksRE5EwVxP0b/GhSfHEs7MSH0keQW6Ei2LhhXV 0+JNVm49IUYCflTl+h/PATzC/+mO8h7NetIMh4pYwhI5lIaDkVaKmQMo5vVmeqOriTJS QnAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@purestorage.com header.s=google header.b=ITYIE18J; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=purestorage.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c15si13311003pgg.446.2018.12.11.17.32.31; Tue, 11 Dec 2018 17:33:03 -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; dkim=pass header.i=@purestorage.com header.s=google header.b=ITYIE18J; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=purestorage.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726251AbeLLBbg (ORCPT + 99 others); Tue, 11 Dec 2018 20:31:36 -0500 Received: from mail-qt1-f193.google.com ([209.85.160.193]:40786 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726201AbeLLBbf (ORCPT ); Tue, 11 Dec 2018 20:31:35 -0500 Received: by mail-qt1-f193.google.com with SMTP id k12so18780596qtf.7 for ; Tue, 11 Dec 2018 17:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=purestorage.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J6fFGJHnjceq1r5h/KuGidS1/t2IUyPSho208krEb6M=; b=ITYIE18JbXHVspKL/CUngrw7avgWXI6uoR+Fi3iNyYSW4olj33rA64fBJuBTt5BkLE wcfblW5f44jUEM9FgP3xLmTZK0KLNBZyhThCff6uH+djYbpneZz8l0ktXPTVH+XYKL4F 4FCkIMoqTqVemDgrZkfGfpjRQul1GSEdNwdzY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J6fFGJHnjceq1r5h/KuGidS1/t2IUyPSho208krEb6M=; b=mgYh6kawv/cTtm4WWCOJaoitmO4zxSIBR/1vTp+o4wxdHY5MYGbb6/RUmg9fa2Wgb3 5mDKJ4R8IQsycrl0nzcOTsCTHT/gRTb6iXoO5+mE21XLK9FkqtJMLlocOWNhbUzczuxJ dSIBNt6xCcn0XxHJbPwO5Oi09y+kF59eLCb2OgGlMtbnqSyRKtge8ZH9HgOwQIFXj1qy SpnlZc7filY9VvsUIsnXqoeq+xsKRtZBO087idiDs+0qW2SzLtMumPteHs1wXgj3+OFj vqu9Yi7GqrDOlhGMoxMRIXfrkLveclLIY4t4+g4Q17kI8tn65iQhxsY3gH2FY8P97TXl 1oXQ== X-Gm-Message-State: AA+aEWYDvmb6nxst5oGVlztfjve6aBSVDxmuvHF3W5jxqIftMgV3o26J cpOX9g44dLLOFznM8wBh5bXFpWszpHPqlG5Iu5mNQZ/wOhs40w== X-Received: by 2002:ac8:18fa:: with SMTP id o55mr18605544qtk.256.1544578294605; Tue, 11 Dec 2018 17:31:34 -0800 (PST) MIME-Version: 1.0 References: <1543535954-28073-1-git-send-email-jalee@purestorage.com> <773bb91f-40a4-a525-f7b8-db821b402821@mellanox.com> In-Reply-To: From: Jaesoo Lee Date: Tue, 11 Dec 2018 17:31:23 -0800 Message-ID: Subject: Re: [PATCH] nvme-rdma: complete requests from ->timeout To: sagi@grimberg.me Cc: nitzanc@mellanox.com, keith.busch@intel.com, axboe@fb.com, hch@lst.de, Roland Dreier , Prabhath Sajeepa , Ashish Karkare , linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Please drop this patch. However, it would be happy if this bug can be fixed as soon as possible. Nitzan, do you mind if you send your patch for review? On Tue, Dec 11, 2018 at 3:39 PM Sagi Grimberg wrote: > > > I cannot reproduce the bug with the patch; in my failure scenarios, it > > seems that completing the request on errors in nvme_rdma_send_done > > makes __nvme_submit_sync_cmd to be unblocked. Also, I think this is > > safe from the double completions. > > > > However, it seems that nvme_rdma_timeout code is still not free from > > the double completion problem. So, it looks promising to me if you > > could separate out the nvme_rdma_wr_error handling code as a new > > patch. > > Guys, can you please send proper patches so we can review properly?