The following commit is in mainline as of v4.2-rc4:

commit f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc
Author: Martin K. Petersen <[email protected]>
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507618

Title:
  Potential raid0 data corruption when using trim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507618/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to