| commit | 9223214e8d757663f366133ba5f9b58aa6b28efb | |
| author | NeilBrown <neilb@cse.unsw.edu.au> | |
| Thu, 18 Aug 2005 18:24:16 +0000 (18 11:24 -0700) | ||
| committer | Linus Torvalds <torvalds@g5.osdl.org> | |
| Thu, 18 Aug 2005 19:53:57 +0000 (18 12:53 -0700) | ||
| tree | b3977e067dbf3b2679c16f77c9e9025c7f71f26f | treesnapshot (tar.gz zip) |
| parent | 60d7603a18a5c07252e7aa0b0e2424315195d4dc | commitdiff |
[PATCH] md: make sure mddev->bitmap_offset gets cleared between array instantiations.
... otherwise we might try to load a bitmap from an array which hasn't one.
The bug is that if you create an array with an internal bitmap, shut it down,
and then create an array with the same md device, the md drive will assume it
should have a bitmap too. As the array can be created with a different md
device, it is mostly an inconvenience. I'm pretty sure there is no risk of
data corruption.
Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
... otherwise we might try to load a bitmap from an array which hasn't one.
The bug is that if you create an array with an internal bitmap, shut it down,
and then create an array with the same md device, the md drive will assume it
should have a bitmap too. As the array can be created with a different md
device, it is mostly an inconvenience. I'm pretty sure there is no risk of
data corruption.
Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| drivers/md/md.c | diffblobblamehistory |