From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Jiazi Li <jqqlijiazi@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"mingzhu.wang" <mingzhu.wang@transsion.com>
Subject: Re: [PATCH] kthread: update comment for __to_kthread
Date: Thu, 19 Jun 2025 12:34:20 -0500 [thread overview]
Message-ID: <877c17zlcz.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20250619120104.4622-1-jqqlijiazi@gmail.com> (Jiazi Li's message of "Thu, 19 Jun 2025 20:00:58 +0800")
Jiazi Li <jqqlijiazi@gmail.com> writes:
> With commit 343f4c49f243 ("kthread: Don't allocate kthread_struct
> for init and umh") and commit 753550eb0ce1 ("fork: Explicitly set
> PF_KTHREAD"), umh task no longer have struct kthread and PF_KTHREAD flag.
> Io_uring worker thread does not have PF_KTHREAD flag, but worker_private
> is not null, so update comment for __to_kthread.
I agree the comment is a bit dated and can use being updated.
Removing the portion describing the exceptions for init and umh is good
as they no longer apply.
However I don't think we want to go on about io_uring and whatever
else winds up using p->worker_private as exceptions. That will just
mean the comment goes stale next time there is a change.
Can you update the comment to describe what the current rules
are to detect is something is a kthread?
Perhaps:
*
* When "(p->flags & PF_KTHREAD)" is set the task is a kthread and will
* always remain a kthread. For kthreads p->worker_private always
* points to a struct kthread. For tasks that are not kthreads
* p->worker_private is used to point to other things.
*
* Return NULL for any task that is not a kthread.
*/
Eric
> Signed-off-by: Jiazi Li <jqqlijiazi@gmail.com>
> Signed-off-by: mingzhu.wang <mingzhu.wang@transsion.com>
> ---
> kernel/kthread.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/kthread.c b/kernel/kthread.c
> index 85fc068f0083..810cc244b81c 100644
> --- a/kernel/kthread.c
> +++ b/kernel/kthread.c
> @@ -88,13 +88,9 @@ static inline struct kthread *to_kthread(struct task_struct *k)
> /*
> * Variant of to_kthread() that doesn't assume @p is a kthread.
> *
> - * Per construction; when:
> - *
> - * (p->flags & PF_KTHREAD) && p->worker_private
> - *
> - * the task is both a kthread and struct kthread is persistent. However
> - * PF_KTHREAD on it's own is not, kernel_thread() can exec() (See umh.c and
> - * begin_new_exec()).
> + * For io_uring worker thread, p->worker_private point to io_worker
> + * struct, but they do not have PF_KTHREAD flag.
> + * Return NULL for such tasks.
> */
> static inline struct kthread *__to_kthread(struct task_struct *p)
> {
next prev parent reply other threads:[~2025-06-19 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 12:00 Jiazi Li
2025-06-19 17:34 ` Eric W. Biederman [this message]
2025-06-20 1:10 ` Jiazi Li
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=877c17zlcz.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=jqqlijiazi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingzhu.wang@transsion.com \
--cc=peterz@infradead.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®