Re: [PATCH] spi: use kthread_create_worker() helper

On Wed, 8 Jul 2020 09:09:00 +0200, Marek Szyprowski wrote: > Since commit 4977caef05aa ("kthread: work could not be queued when worker > being destroyed") there is a warning when kworker is used without the > internal 'task' entry properly initialized. Fix this by using > a kthread_create_worker()

Re: [PATCH] spi: use kthread_create_worker() helper

On Wed 2020-07-08 09:09:00, Marek Szyprowski wrote: > Since commit 4977caef05aa ("kthread: work could not be queued when worker > being destroyed") This commit should disappear from linux-next soon. We did not expect that it would cause these warnings. We first want to fix the callers before we pu

Re: [PATCH] spi: use kthread_create_worker() helper

On Wed, Jul 08, 2020 at 09:09:00AM +0200, Marek Szyprowski wrote: > [ cut here ] > WARNING: CPU: 3 PID: 1 at kernel/kthread.c:817 kthread_queue_work+0xac/0xd4 > Modules linked in: > CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.8.0-rc4-00017-g4977caef05aa #1193 > Hardware nam

[PATCH] spi: use kthread_create_worker() helper

Since commit 4977caef05aa ("kthread: work could not be queued when worker being destroyed") there is a warning when kworker is used without the internal 'task' entry properly initialized. Fix this by using a kthread_create_worker() helper instead of open-coding a kworker initialization. This fixes