diff options
author | Andrei Warkentin <andrey.warkentin@gmail.com> | 2012-04-12 15:55:21 +1000 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2012-04-12 15:55:21 +1000 |
commit | 9e41dd35b39c2cf40767332b8f914d7afe25cc40 (patch) | |
tree | b694a4d27b3fd7beb1881d5ad993303fe7309c59 /drivers/md | |
parent | 5020ad7d143ccfcf8149974096220d59e5572120 (diff) | |
download | linux-9e41dd35b39c2cf40767332b8f914d7afe25cc40.tar.bz2 |
MD: Bitmap version cleanup.
bitmap_new_disk_sb() would still create V3 bitmap superblock
with host-endian layout.
Perhaps I'm confused, but shouldn't bitmap_new_disk_sb() be
creating a V4 bitmap superblock instead, that is portable,
as per comment in bitmap.h?
Signed-off-by: Andrei Warkentin <andrey.warkentin@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
-rw-r--r-- | drivers/md/bitmap.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c index 3d0dfa7a89a2..1c264a701e70 100644 --- a/drivers/md/bitmap.c +++ b/drivers/md/bitmap.c @@ -539,9 +539,6 @@ static int bitmap_new_disk_sb(struct bitmap *bitmap) bitmap->events_cleared = bitmap->mddev->events; sb->events_cleared = cpu_to_le64(bitmap->mddev->events); - bitmap->flags |= BITMAP_HOSTENDIAN; - sb->version = cpu_to_le32(BITMAP_MAJOR_HOSTENDIAN); - kunmap_atomic(sb); return 0; |