diff options
| author | NeilBrown <neilb@suse.de> | 2012-04-12 16:05:06 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-22 16:21:44 -0700 |
| commit | a10d1f32dbf1b9f74b6b6ba1571ee3f7a1bd3883 (patch) | |
| tree | 7d0e3536c79318e029eb41f081b8392ae462846f | |
| parent | 127f90d6ff47e9095261f442d1ad511930cd7fd4 (diff) | |
| download | kernel_samsung_aries-a10d1f32dbf1b9f74b6b6ba1571ee3f7a1bd3883.zip kernel_samsung_aries-a10d1f32dbf1b9f74b6b6ba1571ee3f7a1bd3883.tar.gz kernel_samsung_aries-a10d1f32dbf1b9f74b6b6ba1571ee3f7a1bd3883.tar.bz2 | |
md/bitmap: prevent bitmap_daemon_work running while initialising bitmap
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>
| -rw-r--r-- | drivers/md/bitmap.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c index 703a3fa..2eba9a1 100644 --- a/drivers/md/bitmap.c +++ b/drivers/md/bitmap.c @@ -1897,7 +1897,9 @@ int bitmap_load(mddev_t *mddev) * re-add of a missing device */ start = mddev->recovery_cp; + mutex_lock(&mddev->bitmap_info.mutex); err = bitmap_init_from_disk(bitmap, start); + mutex_unlock(&mddev->bitmap_info.mutex); } if (err) goto out; |