From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] Separate target visibility from reaped state information Date: Wed, 3 Feb 2016 18:17:27 +0100 Message-ID: <20160203171727.GA4828@lst.de> References: <568FE922.9090004@sandisk.com> <1453251809.2320.56.camel@HansenPartnership.com> <20160131185455.00000ef7@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.211]:43140 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933788AbcBCRR3 (ORCPT ); Wed, 3 Feb 2016 12:17:29 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: "Martin K. Petersen" Cc: Sebastian Herbszt , James Bottomley , Bart Van Assche , Christoph Hellwig , Johannes Thumshirn , Dan Williams , "linux-scsi@vger.kernel.org" On Mon, Feb 01, 2016 at 08:11:29PM -0500, Martin K. Petersen wrote: > I am concerned about queuing something as a stable fix if it is just > masking a fundamental underlying problem. It's not masking a fundamental problem. It fixes the target state so that we can mark a starget as being under deletion before we have to drop the list protecting the target list iteration. Independ of any any other scanning changes it is the right thing to do.