Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3579158imu; Sun, 11 Nov 2018 18:32:57 -0800 (PST) X-Google-Smtp-Source: AJdET5cfZfdz4ypo56cviZLicaAFMdRhn18cpiUUmnrmlY4f2yIXPKs2ip3CfpU5kXSPgI6Z5e9G X-Received: by 2002:a62:6181:: with SMTP id v123-v6mr18582563pfb.117.1541989977637; Sun, 11 Nov 2018 18:32:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541989977; cv=none; d=google.com; s=arc-20160816; b=yHtAa20RWnV+KXygynubqchJpIAIB+fsHTCP1c5eo/Jx02q3OtdV5OlF8EpAJ3pHIV NwmotqeP0Uykqz0oieRuXzCV9/tlEGcYQBdi8XQYauh8T0ZUcDYR5WoVwF9xsM88aLfg fvUwjBfKB79M/n7YVf/rhyJMv2zBPbhF6IL8FY09VP/XvF2q0iJhoDTv+rhTcskCEMME z138Zxhxr+/yD9yg3Hzj06YNRxyDF/B1ybkUyxWY03U9JTaxdQsUdC6aW4A0ypcdIsxj D/y556apJ2myEse9iciFjPOIthpRSCZtSCXFnOFNa8N6lMJoi1Qo+nPgZGsasM72FEI8 XaMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=zi+GSxR2IYJ7pTXDU3KPpjzxSTlKfBEty3kMpe53sqU=; b=JJEZnPRJ5aJ0nPtzBZRorLwhDyczjlrnULKbGFfw0YZPFEjCi4LdT3gSUO2oQHP7hX f6RoA1hl/wsJhi7A3ro73KUInXWH/JSldCprEkDpAwe6JfeuE2ca3lUV5akSKlnPLcPL ITdrHcwQ0T+SYazM/38+plZEOxnrqgggl72W5tkkWXpqH+o89S66y5lpaewkRNOo+FWL ZqgM3ZL2P1tSSaTYGSMl0vaCBAcIDTNCqwy+rP2bLwCW4BNM184kFOUWZ/3on+pL1+lu dfO1Xjox2WD4Ls4v9BnyttWq33tgQ1LALDbMWF4bFDv5HfwywEZJ3OEtV8/AfOhqb9XD hAbw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ZCpQ98Mb; 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 g63-v6si16883539pfc.187.2018.11.11.18.32.42; Sun, 11 Nov 2018 18:32:57 -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=@kernel.org header.s=default header.b=ZCpQ98Mb; 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 S1730419AbeKLMXD (ORCPT + 99 others); Mon, 12 Nov 2018 07:23:03 -0500 Received: from mail.kernel.org ([198.145.29.99]:45582 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729612AbeKLMXD (ORCPT ); Mon, 12 Nov 2018 07:23:03 -0500 Received: from localhost (unknown [206.108.79.134]) (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 04B6320871; Mon, 12 Nov 2018 02:32:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541989925; bh=gkzsYs54GGYLBvF4p6dzXo6kbRPQZ+LyXv+aPjJeLYI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZCpQ98MbaFX7dEFQ4ubD2k4vc8oJyD/rUYsHqR6aEG0rKdSlk83BVvGWDNF0J+Vfj 0uxs3hXXek0ctai4Lfs9ioacY1I9BgoCLYjaAHaFuWfAL6fMm53o9Dkvb1a54L+Ooj L2NkgDl1QVN7dta6B/XFRzQJzyJ0Dv460V5ubnUY= Date: Sun, 11 Nov 2018 18:32:04 -0800 From: Greg Kroah-Hartman To: Bart Van Assche Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Sagi Grimberg , Christoph Hellwig , Sasha Levin Subject: Re: [PATCH 4.19 078/361] nvmet-rdma: use a private workqueue for delete Message-ID: <20181112023204.GC28618@kroah.com> References: <20181111221619.915519183@linuxfoundation.org> <20181111221630.901793876@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 11, 2018 at 05:27:05PM -0800, Bart Van Assche wrote: > On 11/11/18 2:17 PM, Greg Kroah-Hartman wrote: > > 4.19-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Sagi Grimberg > > > > [ Upstream commit 2acf70ade79d26b97611a8df52eb22aa33814cd4 ] > > > > Queue deletion is done asynchronous when the last reference on the queue > > is dropped. Thus, in order to make sure we don't over allocate under a > > connect/disconnect storm, we let queue deletion complete before making > > forward progress. > > > > However, given that we flush the system_wq from rdma_cm context which > > runs from a workqueue context, we can have a circular locking complaint > > [1]. Fix that by using a private workqueue for queue deletion. > > Hi Greg, > > You may want to drop this patch. A bug was discovered in this patch a few > days ago. I think not backporting this patch is better than backporting it. > See also the discussion at > http://lists.infradead.org/pipermail/linux-nvme/2018-November/020766.html. A > quote from that e-mail thread: "I think we need to revert 2acf70a > ("nvmet-rdma: use a private workqueue for delete") altogether because it > never made any difference..". Now dropped from the 4.18 and 4.19 queues, thanks. greg k-h