From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com ([192.55.52.93]:7257 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934802AbeFMQxf (ORCPT ); Wed, 13 Jun 2018 12:53:35 -0400 Date: Wed, 13 Jun 2018 10:56:32 -0600 From: Keith Busch To: Ben Hutchings Cc: Jianchao Wang , stable@vger.kernel.org, Sasha Levin , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Subject: Re: [PATCH 4.4 110/268] nvme-pci: Fix nvme queue cleanup if IRQ setup fails Message-ID: <20180613165631.GE5574@localhost.localdomain> References: <20180528100202.045206534@linuxfoundation.org> <20180528100214.621806271@linuxfoundation.org> <1528906474.2289.155.camel@codethink.co.uk> <20180613163007.GD5574@localhost.localdomain> <1528907855.2289.157.camel@codethink.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1528907855.2289.157.camel@codethink.co.uk> Sender: stable-owner@vger.kernel.org List-ID: On Wed, Jun 13, 2018 at 05:37:35PM +0100, Ben Hutchings wrote: > On Wed, 2018-06-13 at 10:30 -0600, Keith Busch wrote: > > Thank you very much the catching that. This particular patch is indeed > > not correct without the following: > > > > � 161b8be2bd6ab ("nvme-pci: initialize queue memory before interrupts") > > Oh, now I see. Do you think that commit is suitable for stable > branches? Yes, we can safely include that commit 4.4-stable. The scenario it fixes isn't very common in 4.4, but it could happen with quirky hardware or legacy interrupts.