diff options
author | Yury Norov <yury.norov@gmail.com> | 2023-02-27 11:24:36 -0800 |
---|---|---|
committer | Yury Norov <yury.norov@gmail.com> | 2023-06-22 13:57:41 -0700 |
commit | c1d2ba10f594046831d14b03f194e8d05e78abad (patch) | |
tree | 6d6ad141cd6405d9620287e868a6b4770578fca8 /include/linux/nodemask.h | |
parent | c4c14c290682e080da5cee81f4998062e1be274a (diff) | |
download | linux-c1d2ba10f594046831d14b03f194e8d05e78abad.tar.gz linux-c1d2ba10f594046831d14b03f194e8d05e78abad.tar.bz2 linux-c1d2ba10f594046831d14b03f194e8d05e78abad.zip |
lib/bitmap: drop optimization of bitmap_{from,to}_arr64
bitmap_{from,to}_arr64() optimization is overly optimistic on 32-bit LE
architectures when it's wired to bitmap_copy_clear_tail().
bitmap_copy_clear_tail() takes care of unused bits in the bitmap up to
the next word boundary. But on 32-bit machines when copying bits from
bitmap to array of 64-bit words, it's expected that the unused part of
a recipient array must be cleared up to 64-bit boundary, so the last 4
bytes may stay untouched when nbits % 64 <= 32.
While the copying part of the optimization works correct, that clear-tail
trick makes corresponding tests reasonably fail:
test_bitmap: bitmap_to_arr64(nbits == 1): tail is not safely cleared: 0xa5a5a5a500000001 (must be 0x0000000000000001)
Fix it by removing bitmap_{from,to}_arr64() optimization for 32-bit LE
arches.
Reported-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/lkml/20230225184702.GA3587246@roeck-us.net/
Fixes: 0a97953fd221 ("lib: add bitmap_{from,to}_arr64")
Signed-off-by: Yury Norov <yury.norov@gmail.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Diffstat (limited to 'include/linux/nodemask.h')
0 files changed, 0 insertions, 0 deletions