Re: [PATCH AUTOSEL 6.2 09/30] cpumask: fix incorrect cpumask scanning result checks

2023-03-19 Thread Linus Torvalds
On Sun, Mar 19, 2023 at 5:53 PM Sasha Levin wrote: > > [ Upstream commit 8ca09d5fa3549d142c2080a72a4c70ce389163cd ] These are technically real fixes, but they are really just "documented behavior" fixes, and don't actually matter unless you also have 596ff4a09b89 ("cpumask: re-introduce constant-

[PATCH AUTOSEL 6.2 09/30] cpumask: fix incorrect cpumask scanning result checks

2023-03-19 Thread Sasha Levin
From: Linus Torvalds [ Upstream commit 8ca09d5fa3549d142c2080a72a4c70ce389163cd ] It turns out that commit 596ff4a09b89 ("cpumask: re-introduce constant-sized cpumask optimizations") exposed a number of cases of drivers not checking the result of "cpumask_next()" and friends correctly. The docu