From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f172.google.com ([209.85.128.172]:36134 "EHLO mail-wr0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751045AbeEBV7z (ORCPT ); Wed, 2 May 2018 17:59:55 -0400 Date: Wed, 2 May 2018 22:59:50 +0100 From: Sudip Mukherjee To: "Martin K. Petersen" Cc: Tejun Heo , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v2] libata: blacklist Micron SSD Message-ID: <20180502215950.GA4621@sudip-laptop> References: <20180429160138.11091-1-sudip.mukherjee@codethink.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: Hi Martin, On Mon, Apr 30, 2018 at 11:24:49PM -0400, Martin K. Petersen wrote: > > Sudip, > > > v1: Only M500IT MU01 was blacklisted. > > > > v2: Whitelist M500IT BG02 and M500DC and then blacklist all other Micron. > > I think my preference would be to blacklist M500IT with the MU01 > firmware (which Micron said was affected) and rely on the "Micron*" > fallthrough further down for the rest. This patch was based on your reply at: https://www.spinics.net/lists/linux-ide/msg55370.html > > I have not gotten firm confirmation on ZRAT behavior so for now we > should probably just do: > > + { "Micron_M500IT_*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM, }, My v1 patch had only MU01 with ATA_HORKAGE_NO_NCQ_TRIM and ATA_HORKAGE_ZERO_AFTER_TRIM. I am not very much confident on only having ATA_HORKAGE_NO_NCQ_TRIM as we have seen huge regression due to 243918be6393 ("libata: Do not blacklist Micron M500DC"). Unless, Micron confirms that it can only have 'ATA_HORKAGE_NO_NCQ_TRIM' I think we should go for both. I don't think we should mark it as ZRAT supported, (without Micron confirmation) and cause another regression. My v1 patch is at https://patchwork.kernel.org/patch/10287605/ Do you want me to resend it again? -- Regards Sudip