From: Hillf Danton <hdanton@sina.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: syzbot <syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] kthread: Unpark only parked kthreads (was Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2))
Date: Thu, 12 Sep 2024 19:30:52 +0800 [thread overview]
Message-ID: <20240912113052.2904-1-hdanton@sina.com> (raw)
In-Reply-To: <ZuGHTBfUlB0qlgn4@localhost.localdomain>
On Wed, 11 Sep 2024 14:04:28 +0200 Frederic Weisbecker <frederic@kernel.org>
>
> Can you test the following?
> ---
One line is needed to feed syzbot including four parts, see below for an example
two keywords tree tag or commit
syz test upstream master
> From: Frederic Weisbecker <frederic@kernel.org>
> Date: Tue, 10 Sep 2024 22:10:19 +0200
> Subject: [PATCH] kthread: Unpark only parked kthreads
>
> Calling into kthread unparking unconditionally is mostly harmless when
> the kthread is already unparked. The wake up is then simply ignored
> because the target is not in TASK_PARKED state.
>
> However if the kthread is per CPU, the wake up is preceded by a call
> to kthread_bind() which expects the task to be inactive and in
> TASK_PARKED state, which obviously isn't the case if it is unparked.
>
> As a result, calling kthread_stop() on an unparked per-cpu kthread
> triggers such a warning:
>
> WARNING: CPU: 0 PID: 11 at kernel/kthread.c:525 __kthread_bind_mask kernel/kthread.c:525
> <TASK>
> kthread_stop+0x17a/0x630 kernel/kthread.c:707
> destroy_workqueue+0x136/0xc40 kernel/workqueue.c:5810
> wg_destruct+0x1e2/0x2e0 drivers/net/wireguard/device.c:257
> netdev_run_todo+0xe1a/0x1000 net/core/dev.c:10693
> default_device_exit_batch+0xa14/0xa90 net/core/dev.c:11769
> ops_exit_list net/core/net_namespace.c:178 [inline]
> cleanup_net+0x89d/0xcc0 net/core/net_namespace.c:640
> process_one_work kernel/workqueue.c:3231 [inline]
> process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
> worker_thread+0x86d/0xd70 kernel/workqueue.c:3393
> kthread+0x2f0/0x390 kernel/kthread.c:389
> ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
> </TASK>
>
> Fix this with skipping unecessary unparking while stopping a kthread.
>
> Reported-by: syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> ---
> kernel/kthread.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/kthread.c b/kernel/kthread.c
> index f7be976ff88a..5e2ba556aba8 100644
> --- a/kernel/kthread.c
> +++ b/kernel/kthread.c
> @@ -623,6 +623,8 @@ void kthread_unpark(struct task_struct *k)
> {
> struct kthread *kthread = to_kthread(k);
>
> + if (!test_bit(KTHREAD_SHOULD_PARK, &kthread->flags))
> + return;
> /*
> * Newly created kthread was parked when the CPU was offline.
> * The binding was lost and we need to set it again.
> --
> 2.46.0
#syz test upstream master
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -623,6 +623,8 @@ void kthread_unpark(struct task_struct *
{
struct kthread *kthread = to_kthread(k);
+ if (!test_bit(KTHREAD_SHOULD_PARK, &kthread->flags))
+ return;
/*
* Newly created kthread was parked when the CPU was offline.
* The binding was lost and we need to set it again.
--
next prev parent reply other threads:[~2024-09-12 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 21:47 [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-07-29 15:48 ` syzbot
2024-07-30 10:22 ` Hillf Danton
2024-07-30 11:00 ` syzbot
2024-07-30 11:30 ` Hillf Danton
2024-07-31 11:05 ` Hillf Danton
2024-07-31 11:29 ` syzbot
2024-09-11 12:04 ` [PATCH] kthread: Unpark only parked kthreads (was Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2)) Frederic Weisbecker
2024-09-12 11:30 ` Hillf Danton [this message]
2024-09-12 14:26 ` [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-09-13 12:11 ` [PATCH] kthread: Unpark only parked kthreads (was Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2)) Hillf Danton
2024-09-13 12:31 ` Frederic Weisbecker
2024-09-13 12:48 ` Hillf Danton
2024-09-13 12:38 ` [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-09-13 13:16 ` Frederic Weisbecker
2024-08-12 4:53 ` syzbot
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=20240912113052.2904-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@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®