From: Yury Norov <yury.norov@gmail.com>
Date: Tue, 28 Jan 2025 16:46:37 +0000 (-0500)
Subject: padata: switch padata_find_next() to using cpumask_next_wrap()
X-Git-Tag: v6.15-rc1~222^2~11
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f954a2d37637b09aed55a4bae769720788633a20;p=thirdparty%2Flinux.git

padata: switch padata_find_next() to using cpumask_next_wrap()

Calling cpumask_next_wrap_old() with starting CPU == -1 effectively means
the request to find next CPU, wrapping around if needed.

cpumask_next_wrap() is the proper replacement for that.

Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
Acked-by: Daniel Jordan <daniel.m.jordan@oracle.com>
Signed-off-by: Yury Norov <yury.norov@gmail.com>
---

diff --git a/kernel/padata.c b/kernel/padata.c
index 78e202fabf90a..b3d4eacc4f5d8 100644
--- a/kernel/padata.c
+++ b/kernel/padata.c
@@ -290,7 +290,7 @@ static struct padata_priv *padata_find_next(struct parallel_data *pd,
 	if (remove_object) {
 		list_del_init(&padata->list);
 		++pd->processed;
-		pd->cpu = cpumask_next_wrap_old(cpu, pd->cpumask.pcpu, -1, false);
+		pd->cpu = cpumask_next_wrap(cpu, pd->cpumask.pcpu);
 	}
 
 	spin_unlock(&reorder->lock);