[SRU][Zesty][PATCH 0/1] md: MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop

[Joseph Salisbury]

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

== SRU Justification ==
The bug reporter was trying to turn on the RAID journal.  One of the steps
is to set the device readonly.  This did not work as planned, or indeed at 
all. After the first --readonly, all requests for the device report 
"No such device or address" until a reboot, though /proc/mdstat says the 
device is still there.

This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but 
upstream 4.10 is EOL, so that is the reason for the SRU request.


== Fix ==
commit 065e519e71b2c1f41936cce75b46b5ab34adb588
Author: NeilBrown <neilb at suse.com>
Date:   Thu Apr 6 11:16:33 2017 +0800

    md: MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop

== Regression Potential ==
This commit was also cc'd to stable and accepted, so additional upstream review
was performed.

== Test Case ==
A test kernel was built with this patch and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.

NeilBrown (1):
  md: MD_CLOSING needs to be cleared after called md_set_readonly or
    do_md_stop

 drivers/md/md.c | 5 +++++
 1 file changed, 5 insertions(+)

-- 
2.7.4