[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220919210559.1509179-1-yury.norov@gmail.com>
Date: Mon, 19 Sep 2022 14:05:52 -0700
From: Yury Norov <yury.norov@...il.com>
To: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Yury Norov <yury.norov@...il.com>
Subject: [PATCH 0/7] cpumask: repair cpumask_check()
After switching cpumask to use nr_cpu_ids in [1], cpumask_check() started
generating many false-positive warnings. There are some more issues with
the cpumask_check() that brake it.
This series fixes cpumask_check() mess and addresses most of the
false-positive warnings observed on boot of x86_64 and arm64.
[1] https://lore.kernel.org/lkml/20220905230820.3295223-4-yury.norov@gmail.com/T/
Yury Norov (7):
cpumask: fix checking valid cpu range
net: fix cpu_max_bits_warn() usage in netif_attrmask_next{,_and}
cpumask: switch for_each_cpu{,_not} to use for_each_bit()
lib/find_bit: add find_next{,_and}_bit_wrap
lib/bitmap: introduce for_each_set_bit_wrap() macro
lib/find: optimize for_each() macros
lib/bitmap: add tests for for_each() iterators
include/linux/cpumask.h | 37 ++----
include/linux/find.h | 140 +++++++++++++++++-----
include/linux/netdevice.h | 10 +-
lib/cpumask.c | 12 +-
lib/test_bitmap.c | 244 +++++++++++++++++++++++++++++++++++++-
5 files changed, 375 insertions(+), 68 deletions(-)
--
2.34.1
Powered by blists - more mailing lists