The following commit is in mainline as of v4.2-rc4:
commit f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc
Author: Martin K. Petersen <martin.peter...@oracle.com>
Date: Wed Jul 22 07:57:12 2015 -0400
block: Do a full clone when splitting discard bios
This commit was also cc'd to stable and has made its way into Vivid via
commit cd57df0 and Wily when it was rebased to 4.2.
This bug should not have affected Trusty since the bug was introduce by
upstream commit: 20d0189b. That commit was applied to mainline in
v3.14-rc1 and Trusty is based on the 3.13 kernel.
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: Confirmed
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Wily)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Vivid)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507618
Title:
Potential raid0 data corruption when using trim
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
Fix Released
Bug description:
There's a scary issue with fstrim on raid0 and raid10 mdadm devices.
It is fixed upstream in linux/4.1.5-1, linux/3.16.7-ckt17-1, but I
can't find anything in the changelogs for ubuntu.
Here's the links:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793326
http://www.spinics.net/lists/raid/msg49440.html
I did my amateur analysis by extracting sources for current trusty
kernel 3.13.0-65-generic and current trusty-lts-utopic
3.16.0-50-generic and looking at files referenced in patches from the
Martin K. Petersen's email, and it appears that 3.16 already has this
fix included, and 3.13 is a completely different code base, so it
isn't clear whether it is affected or not.
I've disabled fstrim in cron until I understand the situation better.
Could someone knowledgeable chime in on the status of this on Ubuntu,
specifically Trusty and after?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507618/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
