From: syzbot <syzbot+b5d7ab56d43de3fd5aac@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, nogikh@google.com,
pimyn@google.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] possible deadlock in tasklet_action_common (2)
Date: Tue, 28 Jul 2026 06:23:01 -0700 [thread overview]
Message-ID: <6a68ad35.073198cf.94f0f.0047.GAE@google.com> (raw)
In-Reply-To: <CAJWNTGxx9QyQjknBHKow5sDrpt6ZEorh9BXVnv9aKNuzYGi=1A@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: 62cc9024 Merge tag 'mm-hotfixes-stable-2026-07-27-14-1..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=177c31b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=abdd1c3924a3d690
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
Note: no patches were applied.
next prev parent reply other threads:[~2026-07-28 13:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJWNTGzO5GGF4X0_QM_XdF=L_Q9mPxtZyrthe8nKKeD5qtqpYQ@mail.gmail.com>
2026-07-28 11:25 ` [syzbot] [input?] possible deadlock in tasklet_action_common (2) syzbot
2026-07-28 11:56 ` Pimyn Girgis
2026-07-28 13:23 ` syzbot [this message]
2026-07-28 13:38 ` Pimyn Girgis
2026-07-28 14:56 ` syzbot
2026-05-20 17:05 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
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=6a68ad35.073198cf.94f0f.0047.GAE@google.com \
--to=syzbot+b5d7ab56d43de3fd5aac@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pimyn@google.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.