[Precise SRU][PATCH 0/1] Possible corruption of array metadata on shutdown

Luis Henriques luis.henriques at canonical.com
Mon Apr 30 16:46:25 UTC 2012

BugLink: http://bugs.launchpad.net/bugs/992038

== Precise SRU Justification ==

Commit c744a65c1e2d59acc54333ce8 introduced the possibility of array
metadata be corrupted.  This commit has reached precise through stable
kernel updates.  The fix is already available upstreams in commit
30b8aa9172dfeaac6d77897c67ee9f9fc574cdbb (3.4-rc1) but is not
available in stable yet.

== Fix ==

Commit 30b8aa9172dfeaac6d77897c67ee9f9fc574cdbb fixes this issue.

== Impact ==

The issue has been reported here
http://thread.gmane.org/gmane.linux.raid/38151 and the impact may be
high as it can cause severe data loss.

== Test Case ==

>From the fix description:

    "If, when md_notify_reboot gets the mddev lock, the array is
    in a state where it is assembled but hasn't been started (as can
    happen if the personality module is not available, or in other unusual
    situations), then incorrect metadata will be written out making it
    impossible to re-assemble the array."

NeilBrown (1):
  UBUNTU: SAUCE: md: fix possible corruption of array metadata on

 drivers/md/md.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


More information about the kernel-team mailing list