Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

Broken libata blacklist in 3.17

Posted Oct 7, 2014 22:40 UTC (Tue) by hmh (subscriber, #3838)
Parent article: The 3.17 kernel is out

Or wait for 3.17.1 before you try the shiny new kernel if any of your devices need the libata blacklist...

For example, owners of Micron/Crucial MX500 and MX550 SSDs must _not_ use kernel 3.17 without the above fix, on pain of data loss:
https://bugzilla.kernel.org/show_bug.cgi?id=71371

(Log in to post comments)

Posted Oct 8, 2014 21:58 UTC (Wed) by NightMonkey (subscriber, #23051) [Link]

I just never use a .0 kernel release. If I'm impatient, I'll go with .1, and if not, wait for .2 and beyond. :)

Broken libata blacklist in 3.17 AND 3.17.1

Posted Oct 13, 2014 11:05 UTC (Mon) by hmh (subscriber, #3838) [Link]

The fix is unlikely to be in 3.17.1. Beware.

Broken libata blacklist in 3.17, fixed in 3.17.1

Posted Oct 15, 2014 10:59 UTC (Wed) by hmh (subscriber, #3838) [Link]

Fortunately, there was enough time for it to be late-added to 3.17.1, so kernel 3.17.1 fixes the issue.