From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+b5d7ab56d43de3fd5aac@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] possible deadlock in tasklet_action_common (2)
Date: Sun, 26 Jul 2026 10:07:56 +0800 [thread overview]
Message-ID: <20260726020807.722-1-hdanton@sina.com> (raw)
In-Reply-To: <6a655704.70955b6c.323240.0028.GAE@google.com>
> Date: Sat, 25 Jul 2026 17:38:28 -0700 [thread overview]
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: cc2b5f627e8c Add linux-next specific files for 20260714
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13d446b9580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2290ccbf984c524f
> dashboard link: https://syzkaller.appspot.com/bug?extid=b5d7ab56d43de3fd5aac
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1310a232580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13c3b2ea580000
#syz test
--- x/kernel/softirq.c
+++ y/kernel/softirq.c
@@ -924,7 +924,6 @@ static void tasklet_action_common(struct
tl_head->tail = &tl_head->head;
local_irq_enable();
- tasklet_lock_callback();
while (list) {
struct tasklet_struct *t = list;
@@ -944,7 +943,6 @@ static void tasklet_action_common(struct
}
}
tasklet_unlock(t);
- tasklet_callback_sync_wait_running();
continue;
}
tasklet_unlock(t);
@@ -957,7 +955,6 @@ static void tasklet_action_common(struct
__raise_softirq_irqoff(softirq_nr);
local_irq_enable();
}
- tasklet_unlock_callback();
}
static __latent_entropy void tasklet_action(void)
@@ -1006,11 +1003,10 @@ void tasklet_unlock_spin_wait(struct tas
while (test_bit(TASKLET_STATE_RUN, &(t)->state)) {
if (IS_ENABLED(CONFIG_PREEMPT_RT)) {
/*
- * Prevent a live lock when current preempted soft
- * interrupt processing or prevents ksoftirqd from
- * running.
+ * wait_on_bit(TASKLET_STATE_RUN)
+ * https://lore.kernel.org/lkml/20260524004526.1046-1-hdanton@sina.com/
*/
- tasklet_callback_cancel_wait_running();
+ tasklet_unlock_wait(t);
} else {
cpu_relax();
}
--
next prev parent reply other threads:[~2026-07-26 2:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:05 [syzbot] [input?] possible deadlock in tasklet_action_common (2) syzbot
2026-05-21 1:52 ` Hillf Danton
2026-05-21 14:34 ` Sebastian Andrzej Siewior
2026-05-21 22:35 ` Hillf Danton
2026-05-22 6:39 ` Sebastian Andrzej Siewior
2026-05-22 7:21 ` Hillf Danton
2026-05-22 7:35 ` Sebastian Andrzej Siewior
2026-05-24 0:45 ` Hillf Danton
2026-07-26 0:38 ` syzbot
2026-07-26 2:07 ` Hillf Danton [this message]
2026-07-26 3:16 ` syzbot
2026-07-26 4:11 ` Hillf Danton
2026-07-26 4:47 ` 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=20260726020807.722-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+b5d7ab56d43de3fd5aac@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.