Message ID | 20180429160138.11091-1-sudip.mukherjee@codethink.co.uk |
---|---|
State | Not Applicable |
Delegated to: | David Miller |
Headers | show |
Series | [v2] libata: blacklist Micron SSD | expand |
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. 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, },
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 -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Sudip, >> 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 Yep, but they have confirmed it's only that model and firmware rev that's affected. I just haven't gotten the comprehensive matrix of all current models and firmware revs I was hoping for.
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c index 8bc71ca61e7f..df5d716c0a07 100644 --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -4550,7 +4550,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = { ATA_HORKAGE_NOLPM, }, /* devices that don't properly handle queued TRIM commands */ - { "Micron_M500_*", NULL, ATA_HORKAGE_NO_NCQ_TRIM | + { "Micron_M500DC*", NULL, 0}, + { "Micron_M500IT_*", "MG02", 0}, + { "Micron_M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM | ATA_HORKAGE_ZERO_AFTER_TRIM, }, { "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM | ATA_HORKAGE_ZERO_AFTER_TRIM, },