The patch titled
md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs fix
has been added to the -mm tree. Its filename is
md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs-fix.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs fix
From: Neil Brown <neilb@xxxxxxx>
Avoid a deadlock when removing a device from an md array via sysfs. - fix
Make sure any delayed_delete calls finish before module unload.
For simplicity, flush the queue when we stop the array.
Signed-off-by: Neil Brown <neilb@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/md/md.c | 3 +++
1 files changed, 3 insertions(+)
diff -puN drivers/md/md.c~md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs-fix drivers/md/md.c
--- a/drivers/md/md.c~md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs-fix
+++ a/drivers/md/md.c
@@ -3400,6 +3400,9 @@ static int do_md_stop(mddev_t * mddev, i
sysfs_remove_link(&mddev->kobj, nm);
}
+ /* make sure all delayed_delete calls have finished */
+ flush_scheduled_work();
+
export_array(mddev);
mddev->array_size = 0;
_
Patches currently in -mm which might be from neilb@xxxxxxx are
origin.patch
md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs.patch
md-avoid-a-deadlock-when-removing-a-device-from-an-md-array-via-sysfs-fix.patch
net-sunrpc-svcsockc-fix-a-check.patch
fix-quadratic-behavior-of-shrink_dcache_parent.patch
fix-__d_path-for-lazy-unmounts-and-make-it-unambiguous.patch
the-nfsv2-nfsv3-server-does-not-handle-zero-length-write.patch
readahead-nfsd-case.patch
drivers-mdc-use-array_size-macro-when-appropriate.patch
md-dm-reduce-stack-usage-with-stacked-block-devices.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
