From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 9AAC81A04D3 for ; Fri, 2 Oct 2015 23:04:00 +1000 (AEST) Subject: Re: [PATCH v5 05/34] cxlflash: Fix data corruption when vLUN used over multiple cards To: "Matthew R. Ochs" , linux-scsi@vger.kernel.org, James Bottomley , "Nicholas A. Bellinger" , Brian King , Ian Munsie , Daniel Axtens , Andrew Donnellan , David Laight References: <1443714773-9176-1-git-send-email-mrochs@linux.vnet.ibm.com> <1443714908-13176-1-git-send-email-mrochs@linux.vnet.ibm.com> Cc: Michael Neuling , linuxppc-dev@lists.ozlabs.org, "Manoj N. Kumar" From: Tomas Henzl Message-ID: <560E80BA.90906@redhat.com> Date: Fri, 2 Oct 2015 15:03:54 +0200 MIME-Version: 1.0 In-Reply-To: <1443714908-13176-1-git-send-email-mrochs@linux.vnet.ibm.com> Content-Type: text/plain; charset=windows-1252 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 1.10.2015 17:55, Matthew R. Ochs wrote: > If the same virtual LUN is accessed over multiple cards, only accesses > made over the first card will be valid. Accesses made over the second > card will go to the wrong LUN causing data corruption. > > This is because the global LUN's mode word was being used to determine > whether the LUN table for that card needs to be programmed. The mode > word would be setup by the first card, causing the LUN table for the > second card to not be programmed. > > By unconditionally initializing the LUN table (not depending on the > mode word), the problem is avoided. > > Signed-off-by: Matthew R. Ochs > Signed-off-by: Manoj N. Kumar > Reviewed-by: Brian King Reviewed-by: Tomas Henzl Tomas