diff options
| author | NeilBrown <neilb@suse.de> | 2012-07-19 15:59:18 +1000 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-07-19 15:59:18 +1000 |
| commit | 25f7fd470bc97bb93d3a674e8c56c4a29063ec97 (patch) | |
| tree | 010d5b5cd9ef0d78da903d0baaff15858c40b20d /drivers/md | |
| parent | 84a1caf1453c3d44050bd22db958af4a7f99315c (diff) | |
| download | kernel_goldelico_gta04-25f7fd470bc97bb93d3a674e8c56c4a29063ec97.zip kernel_goldelico_gta04-25f7fd470bc97bb93d3a674e8c56c4a29063ec97.tar.gz kernel_goldelico_gta04-25f7fd470bc97bb93d3a674e8c56c4a29063ec97.tar.bz2 | |
md: fix bug in handling of new_data_offset
commit c6563a8c38fde3c1c7fc925a10bde3ca20799301
md: add possibility to change data-offset for devices.
introduced a 'new_data_offset' attribute which should normally
be the same as 'data_offset', but can be explicitly set to a different
value to allow a reshape operation to move the data.
Unfortunately when the 'data_offset' is explicitly set through
sysfs, the new_data_offset is not also set, so the two would become
out-of-sync incorrectly.
One result of this is that trying to set the 'size' after the
'data_offset' would fail because it is not permitted to set the size
when the 'data_offset' and 'new_data_offset' are different - as that
can be confusing.
Consequently when mdadm tried to do this while assembling an IMSM
array it would fail.
This bug was introduced in 3.5-rc1.
Reported-by: Brian Downing <bdowning@lavos.net>
Bisected-by: Brian Downing <bdowning@lavos.net>
Tested-by: Brian Downing <bdowning@lavos.net>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
| -rw-r--r-- | drivers/md/md.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/md.c b/drivers/md/md.c index a4c219e..0c1fe4cb 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -2931,6 +2931,7 @@ offset_store(struct md_rdev *rdev, const char *buf, size_t len) * can be sane */ return -EBUSY; rdev->data_offset = offset; + rdev->new_data_offset = offset; return len; } |