From: syzbot <syzbot+bd936ccd4339cea66e6b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] possible deadlock in padata_do_serial
Date: Mon, 03 Nov 2025 06:44:02 -0800 [thread overview]
Message-ID: <6908bfb2.050a0220.98a6.003d.GAE@google.com> (raw)
In-Reply-To: <e7958eb8-05f8-48a7-ae71-bc15af6abcf2@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+bd936ccd4339cea66e6b@syzkaller.appspotmail.com
Tested-by: syzbot+bd936ccd4339cea66e6b@syzkaller.appspotmail.com
Tested on:
commit: 6146a0f1 Linux 6.18-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16836342580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f009a9a8d50667
dashboard link: https://syzkaller.appspot.com/bug?extid=bd936ccd4339cea66e6b
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11f3cc2c580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-11-03 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 4:49 [syzbot] [crypto?] possible deadlock in padata_do_serial syzbot
2025-09-11 21:38 ` syzbot
2025-11-03 14:24 ` Tetsuo Handa
2025-11-03 14:44 ` syzbot [this message]
2025-11-04 11:44 ` padata: Is padata_find_next() thread-safe? Tetsuo Handa
2025-11-06 9:28 ` Herbert Xu
2025-11-06 9:41 ` Tetsuo Handa
2025-11-06 9:46 ` Herbert Xu
2025-11-06 11:20 ` [PATCH] padata: use different lock_class_key for padata_list lock Tetsuo Handa
2025-11-07 14:49 ` [PATCH v2] padata: remove __padata_list_init() Tetsuo Handa
2025-11-14 10:23 ` Herbert Xu
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=6908bfb2.050a0220.98a6.003d.GAE@google.com \
--to=syzbot+bd936ccd4339cea66e6b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox