From: Bradley Morgan <include@grrlz.net>
To: linux-kernel@vger.kernel.org
Cc: brads@mainlining.org
Subject: [RESEND PATCH 0/5] kthread: remove worker->task self-assignment
Date: Sat, 29 Aug 2026 16:11:50 +0000 [thread overview]
Message-ID: <20260829161150.16301-1-include@grrlz.net> (raw)
From: Bradley Morgan <brads@mainlining.org>
Resent as a proper series with cover letter. The first send went out as
five separate threads instead of one.
kthread_worker_fn() has carried a FIXME for a decade: it assigns
worker->task = current because the old kthread_run(kthread_worker_fn)
callers never told the worker what task it was. The new
kthread_create_worker*() API sets worker->task before the worker even
starts, so the self-assignment is dead code.
Four drivers were still on the old API. Convert them, then remove the
FIXME.
No functional change intended.
Bradley Morgan (5):
media: ivtv: convert to kthread_run_worker
net: encx24j600: convert to kthread_run_worker
tty: sc16is7xx: convert to kthread_run_worker
cpufreq: schedutil: convert to kthread_create_worker
kthread: remove worker->task self-assignment
drivers/media/pci/ivtv/ivtv-driver.c | 11 ++++-------
drivers/media/pci/ivtv/ivtv-driver.h | 3 +--
drivers/net/ethernet/microchip/encx24j600.c | 12 ++++--------
drivers/tty/serial/sc16is7xx.c | 17 +++++++----------
kernel/sched/cpufreq_schedutil.c | 14 +++++--------
kernel/kthread.c | 7 -------
6 files changed, 21 insertions(+), 63 deletions(-)
next reply other threads:[~2026-08-29 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 16:11 Bradley Morgan [this message]
2026-08-29 16:13 ` [PATCH 1/5] media: ivtv: convert to kthread_run_worker Bradley Morgan
2026-08-29 16:15 ` [PATCH 2/5] net: encx24j600: " Bradley Morgan
2026-08-29 16:16 ` [PATCH 3/5] tty: sc16is7xx: " Bradley Morgan
2026-08-29 16:17 ` [PATCH 4/5] cpufreq: schedutil: convert to kthread_create_worker Bradley Morgan
2026-08-29 16:18 ` [PATCH] kthread: remove worker->task self-assignment Bradley Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260829161150.16301-1-include@grrlz.net \
--to=include@grrlz.net \
--cc=brads@mainlining.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®