[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <64c234af-5141-4062-9170-2122c3edf088@stanley.mountain>
Date: Fri, 13 Dec 2024 17:25:02 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>, Chen Yu <yu.c.chen@...el.com>,
Yafang Shao <laoar.shao@...il.com>,
Mickaël Salaün <mic@...ikod.net>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: [PATCH next] kthread: Fix a NULL vs IS_ERR() bug
The kthread_create_worker_on_node() function returns error pointers,
never NULL. Fix the check to match.
Fixes: e9853c812f86 ("treewide: Introduce kthread_run_worker[_on_cpu]()")
Signed-off-by: Dan Carpenter <dan.carpenter@...aro.org>
---
kernel/kthread.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/kthread.c b/kernel/kthread.c
index 83bf73d2355c..922f15762ec3 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -1124,7 +1124,7 @@ kthread_create_worker_on_cpu(int cpu, unsigned int flags,
struct kthread_worker *worker;
worker = kthread_create_worker_on_node(flags, cpu_to_node(cpu), namefmt, cpu);
- if (worker)
+ if (!IS_ERR(worker))
kthread_bind(worker->task, cpu);
return worker;
--
2.45.2
Powered by blists - more mailing lists