bitmap: Fix return values to be unsigned
authorKees Cook <keescook@chromium.org>
Wed, 18 May 2022 20:52:22 +0000 (13:52 -0700)
committerYury Norov <yury.norov@gmail.com>
Fri, 3 Jun 2022 13:52:58 +0000 (06:52 -0700)
commit005f17007f47495dbbb659aa5db7e581065d16e7
tree96a1096bc13d7c9d54cede10e5f4b005db5b3b16
parentd603fd8dd35f6028bb09cd2e9ec6557c4bc0dd95
bitmap: Fix return values to be unsigned

Both nodemask and bitmap routines had mixed return values that provided
potentially signed return values that could never happen. This was
leading to the compiler getting confusing about the range of possible
return values (it was thinking things could be negative where they could
not be). In preparation for fixing nodemask, fix all the bitmap routines
that should be returning unsigned (or bool) values.

Cc: Yury Norov <yury.norov@gmail.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Christophe de Dinechin <dinechin@redhat.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Yury Norov <yury.norov@gmail.com>
include/linux/bitmap.h
lib/bitmap.c
tools/include/linux/bitmap.h
tools/lib/bitmap.c