md/bitmap: prevent bitmap_daemon_work running while initialising bitmap
authorNeilBrown <neilb@suse.de>
Thu, 12 Apr 2012 06:05:06 +0000 (16:05 +1000)
committerLuis Henriques <luis.henriques@canonical.com>
Mon, 30 Apr 2012 18:15:06 +0000 (19:15 +0100)
commit3f9e80c2184f2d5321639c9e283823e9e35ad89e
tree7f54dedfe1da12d212b9bd21c4766cce8e2b6e59
parent7ccc6be8a1f1e7cc4d73eb5e6f91cc6aba73ef9e
md/bitmap: prevent bitmap_daemon_work running while initialising bitmap

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

commit afbaa90b80b1ec66e5137cc3824746bfdf559b18 upstream.

If a bitmap is added while the array is active, it is possible
for bitmap_daemon_work to run while the bitmap is being
initialised.
This is particularly a problem if bitmap_daemon_work sees
bitmap->filemap as non-NULL before it has been filled in properly.
So hold bitmap_info.mutex while filling in ->filemap
to prevent problems.

This patch is suitable for any -stable kernel, though it might not
apply cleanly before about 3.1.

Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
drivers/md/bitmap.c