public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Pawel Zmarzly <pzmarzly@meta.com>, Niklas.Cassel@wdc.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ata: Disable NCQ_TRIM on Micron 1100 drives
Date: Sat, 2 Sep 2023 12:11:23 +0900	[thread overview]
Message-ID: <b3bb71ed-2303-d715-2efe-4fac8e6048d9@kernel.org> (raw)
In-Reply-To: <91dc19a5-ea7f-1abf-1c35-5a9582036b83@kernel.org>

On 9/2/23 11:54, Damien Le Moal wrote:
> On 9/2/23 05:02, Pawel Zmarzly wrote:
>> Micron 1100 drives lock up when encountering queued TRIM command.
>> It is a quite old hardware series, for past years we have been
>> running our machines with these drives using
>> libata.force=noncqtrim.
>>
>> Signed-off-by: Pawel Zmarzly <pzmarzly@meta.com>
> 
> This does not apply cleanly on the fo-6.6 branch. Can you rebase your patch
> please and make sure it applies to libata tree for-6.6 branch ?

Don't bother. I applied the patch manually with some minor tweaks.
It is now queued for 6.6. Thanks.

> 
>> ---
>> V1 -> V2: Fixed formatting.
>> V2 -> V3: Added missing Signed off line. Sorry, this is my
>> first time upstreaming.
>>
>>  drivers/ata/libata-core.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>> index 175b2a9dc000..116f5fd6e3f7 100644
>> --- a/drivers/ata/libata-core.c
>> +++ b/drivers/ata/libata-core.c
>> @@ -4564,6 +4564,8 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
>>  						ATA_HORKAGE_ZERO_AFTER_TRIM, },
>>  	{ "FCCT*M500*",			NULL,	ATA_HORKAGE_NO_NCQ_TRIM |
>>  						ATA_HORKAGE_ZERO_AFTER_TRIM, },
>> +	{ "Micron_1100_*",		NULL,	ATA_HORKAGE_NO_NCQ_TRIM |
>> +						ATA_HORKAGE_ZERO_AFTER_TRIM, },
>>
>>  	/* devices that don't properly handle TRIM commands */
>>  	{ "SuperSSpeed S238*",		NULL,	ATA_HORKAGE_NOTRIM, },
>> --
>> 2.39.3
> 

-- 
Damien Le Moal
Western Digital Research


      reply	other threads:[~2023-09-02  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  0:02 [PATCH] ata: Disable NCQ_TRIM on Micron 1100 drives Pawel Zmarzly
2023-09-01  9:49 ` Niklas Cassel
2023-09-01 18:23   ` [PATCH v2] " Pawel Zmarzly
2023-09-01 18:51     ` Niklas Cassel
2023-09-01 20:02       ` [PATCH v3] " Pawel Zmarzly
2023-09-01 20:19         ` Niklas Cassel
2023-09-02  2:54         ` Damien Le Moal
2023-09-02  3:11           ` Damien Le Moal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b3bb71ed-2303-d715-2efe-4fac8e6048d9@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pzmarzly@meta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox