| commit | 0bdb50c531f7377a9da80d3ce2d61f389c84cb30 | |
| author | NeilBrown <neil@brown.name> | |
| Sun, 6 Jan 2019 10:06:25 +0000 (6 21:06 +1100) | ||
| committer | Mike Snitzer <snitzer@redhat.com> | |
| Tue, 5 Mar 2019 19:48:52 +0000 (5 14:48 -0500) | ||
| tree | 73c7dc72106541c696fa61e40c2484eddd443987 | treesnapshot (tar.gz zip) |
| parent | d2832376b69e1e02cae0de660ab7c03223f09341 | commitdiff |
dm: fix to_sector() for 32bit
A dm-raid array with devices larger than 4GB won't assemble on
a 32 bit host since _check_data_dev_sectors() was added in 4.16.
This is because to_sector() treats its argument as an "unsigned long"
which is 32bits (4GB) on a 32bit host. Using "unsigned long long"
is more correct.
Kernels as early as 4.2 can have other problems due to to_sector()
being used on the size of a device.
Fixes: 0cf4503174c1 ("dm raid: add support for the MD RAID0 personality")
cc: stable@vger.kernel.org (v4.2+)
Reported-and-tested-by: Guillaume Perréal <gperreal@free.fr>
Signed-off-by: NeilBrown <neil@brown.name>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
A dm-raid array with devices larger than 4GB won't assemble on
a 32 bit host since _check_data_dev_sectors() was added in 4.16.
This is because to_sector() treats its argument as an "unsigned long"
which is 32bits (4GB) on a 32bit host. Using "unsigned long long"
is more correct.
Kernels as early as 4.2 can have other problems due to to_sector()
being used on the size of a device.
Fixes: 0cf4503174c1 ("dm raid: add support for the MD RAID0 personality")
cc: stable@vger.kernel.org (v4.2+)
Reported-and-tested-by: Guillaume Perréal <gperreal@free.fr>
Signed-off-by: NeilBrown <neil@brown.name>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
| include/linux/device-mapper.h | diffblobblamehistory |