From: Alice Ryhl <aliceryhl@google.com>
To: brauner@kernel.org
Cc: broonie@kernel.org, davidgow@google.com, gtucker@gtucker.io,
jack@suse.cz, kunit-dev@googlegroups.com,
linux-fsdevel@vger.kernel.org, mjguzik@gmail.com, tj@kernel.org,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
Alice Ryhl <aliceryhl@google.com>
Subject: Re: make_task_dead() & kthread_exit()
Date: Tue, 3 Mar 2026 10:03:28 +0000 [thread overview]
Message-ID: <20260303100328.1378655-1-aliceryhl@google.com> (raw)
In-Reply-To: <20260226-ungeziefer-erzfeind-13425179c7b2@brauner>
Christian Brauner <brauner@kernel.org> writes:
> Oh nice.
> I was kinda hoping Tejun would jump on this one and so just pointed to
> one potential way to fix it but didn't really spend time on it.
>
> Anyway, let's just take what you proposed and slap a commit message on
> it. Fwiw, init_task does have ->worker_private it just gets set later
> during sched_init():
>
> /*
> * The idle task doesn't need the kthread struct to function, but it
> * is dressed up as a per-CPU kthread and thus needs to play the part
> * if we want to avoid special-casing it in code that deals with per-CPU
> * kthreads.
> */
> WARN_ON(!set_kthread_struct(current));
>
> I think that @current here is misleading. When sched_init() runs it
> should be single-threaded still and current == &init_task. So that
> set_kthread_struct(current) call sets @init_task's worker_private iiuc.
>
> Patch appended. I'll stuff it into vfs.fixes.
welp, I guess you get another one here:
Tested-by: Alice Ryhl <aliceryhl@google.com>
from:
https://lore.kernel.org/all/aaaxK5gFWN70WmMn@google.com/
Alice
next prev parent reply other threads:[~2026-03-03 10:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 14:52 [PATCH RFC v2] pidfs: convert rb-tree to rhashtable Christian Brauner
2026-01-20 15:43 ` Mateusz Guzik
2026-01-21 10:59 ` Jan Kara
2026-01-22 10:18 ` Christian Brauner
2026-01-22 13:21 ` Jan Kara
2026-02-20 15:11 ` Guillaume Tucker
2026-02-24 13:22 ` Christian Brauner
2026-02-24 16:25 ` make_task_dead() & kthread_exit() Christian Brauner
2026-02-24 17:04 ` Mark Brown
2026-02-24 18:27 ` Guillaume Tucker
2026-02-24 19:30 ` Linus Torvalds
2026-02-26 4:09 ` David Gow
2026-02-26 9:47 ` Christian Brauner
2026-02-27 16:54 ` Linus Torvalds
2026-03-03 10:03 ` Alice Ryhl [this message]
2026-03-06 11:05 ` Christian Loehle
2026-03-06 16:28 ` Linus Torvalds
2026-02-26 4:08 ` David Gow
2026-02-24 16:37 ` [PATCH RFC v2] pidfs: convert rb-tree to rhashtable Mark Brown
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=20260303100328.1378655-1-aliceryhl@google.com \
--to=aliceryhl@google.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=davidgow@google.com \
--cc=gtucker@gtucker.io \
--cc=jack@suse.cz \
--cc=kunit-dev@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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