diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2009-07-23 20:30:42 +0100 |
|---|---|---|
| committer | Alasdair G Kergon <agk@redhat.com> | 2009-07-23 20:30:42 +0100 |
| commit | 5dea271b6d87bd1d79a59c1d5baac2596a841c37 (patch) | |
| tree | c85bcee4f90729927285fc282c6df94bf18d023d /drivers/md/dm-crypt.c | |
| parent | a732c207d19e899845ae47139708af898daaf9fd (diff) | |
| download | kernel_samsung_smdk4412-5dea271b6d87bd1d79a59c1d5baac2596a841c37.zip kernel_samsung_smdk4412-5dea271b6d87bd1d79a59c1d5baac2596a841c37.tar.gz kernel_samsung_smdk4412-5dea271b6d87bd1d79a59c1d5baac2596a841c37.tar.bz2 | |
dm table: pass correct dev area size to device_area_is_valid
Incorrect device area lengths are being passed to device_area_is_valid().
The regression appeared in 2.6.31-rc1 through commit
754c5fc7ebb417b23601a6222a6005cc2e7f2913.
With the dm-stripe target, the size of the target (ti->len) was used
instead of the stripe_width (ti->len/#stripes). An example of a
consequent incorrect error message is:
device-mapper: table: 254:0: sdb too small for target
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Diffstat (limited to 'drivers/md/dm-crypt.c')
| -rw-r--r-- | drivers/md/dm-crypt.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c index 529e2ba..ed10381 100644 --- a/drivers/md/dm-crypt.c +++ b/drivers/md/dm-crypt.c @@ -1318,7 +1318,7 @@ static int crypt_iterate_devices(struct dm_target *ti, { struct crypt_config *cc = ti->private; - return fn(ti, cc->dev, cc->start, data); + return fn(ti, cc->dev, cc->start, ti->len, data); } static struct target_type crypt_target = { |