From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation Date: Wed, 03 Feb 2016 21:48:45 -0500 Message-ID: References: <1453473761-54777-1-git-send-email-hare@suse.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from userp1040.oracle.com ([156.151.31.81]:43578 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756441AbcBDCs6 (ORCPT ); Wed, 3 Feb 2016 21:48:58 -0500 In-Reply-To: <1453473761-54777-1-git-send-email-hare@suse.de> (Hannes Reinecke's message of "Fri, 22 Jan 2016 15:42:41 +0100") Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Hannes Reinecke Cc: "Martin K. Petersen" , Christoph Hellwig , James Bottomley , linux-scsi@vger.kernel.org >>>>> "Hannes" == Hannes Reinecke writes: Hannes> If MODE SELECT returns with sense '05/91/36' (command lock Hannes> violation) it should always be retried without counting the Hannes> number of retries. During an HBA upgrade or similar Hannes> circumstances one might see a flood of MODE SELECT command from Hannes> various HBAs, which will easily trigger the sense code and Hannes> exceed the retry count. Should this be Cc: stable? -- Martin K. Petersen Oracle Linux Engineering