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 754c5fc7. 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>
Showing
- drivers/md/dm-crypt.c 1 addition, 1 deletiondrivers/md/dm-crypt.c
- drivers/md/dm-delay.c 2 additions, 2 deletionsdrivers/md/dm-delay.c
- drivers/md/dm-linear.c 1 addition, 1 deletiondrivers/md/dm-linear.c
- drivers/md/dm-mpath.c 1 addition, 1 deletiondrivers/md/dm-mpath.c
- drivers/md/dm-raid1.c 1 addition, 1 deletiondrivers/md/dm-raid1.c
- drivers/md/dm-stripe.c 4 additions, 3 deletionsdrivers/md/dm-stripe.c
- drivers/md/dm-table.c 5 additions, 5 deletionsdrivers/md/dm-table.c
- include/linux/device-mapper.h 2 additions, 2 deletionsinclude/linux/device-mapper.h
Loading
Please register or sign in to comment