This is a note to let you know that I've just added the patch titled

    libata: disable queued TRIM for Crucial M500 mSATA SSDs

to the 3.13-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     libata-disable-queued-trim-for-crucial-m500-msata-ssds.patch
and it can be found in the queue-3.13 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 2564338b13e6e132ee224edb63e1e872adf431f4 Mon Sep 17 00:00:00 2001
From: Marios Andreopoulos <[email protected]>
Date: Mon, 3 Mar 2014 18:19:59 +0200
Subject: libata: disable queued TRIM for Crucial M500 mSATA SSDs

From: Marios Andreopoulos <[email protected]>

commit 2564338b13e6e132ee224edb63e1e872adf431f4 upstream.

Queued TRIM commands cause problems and silent file system corruption
on Crucial M500 SSDs. This patch disables them for the mSATA model of
the drive.

Signed-off-by: Marios Andreopoulos <[email protected]>
Signed-off-by: Tejun Heo <[email protected]>
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=71371
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/ata/libata-core.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -4225,6 +4225,7 @@ static const struct ata_blacklist_entry
        /* devices that don't properly handle queued TRIM commands */
        { "Micron_M500*",               NULL,   ATA_HORKAGE_NO_NCQ_TRIM, },
        { "Crucial_CT???M500SSD1",      NULL,   ATA_HORKAGE_NO_NCQ_TRIM, },
+       { "Crucial_CT???M500SSD3",      NULL,   ATA_HORKAGE_NO_NCQ_TRIM, },
 
        /*
         * Some WD SATA-I drives spin up and down erratically when the link


Patches currently in stable-queue which might be from [email protected] 
are

queue-3.13/libata-disable-queued-trim-for-crucial-m500-msata-ssds.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to