From: syzbot <syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com>
To: axboe@kernel.dk, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (6)
Date: Wed, 21 Jan 2026 18:40:02 -0800 [thread overview]
Message-ID: <69718e02.050a0220.706b.0020.GAE@google.com> (raw)
In-Reply-To: <e2eead9d-c355-4e94-af91-c9c60c9bd445@kernel.dk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com
Tested-by: syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com
Tested on:
commit: 57ab5080 io_uring/io-wq: don't trigger hung task for s..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git syztest
console output: https://syzkaller.appspot.com/x/log.txt?x=132ef3fa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f75eb998b5774eb
dashboard link: https://syzkaller.appspot.com/bug?extid=4eb282331cab6d5b6588
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-01-22 2:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2eead9d-c355-4e94-af91-c9c60c9bd445@kernel.dk>
2026-01-22 2:40 ` syzbot [this message]
2025-08-18 8:05 [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (6) syzbot
2026-01-20 3:48 ` Jens Axboe
2026-01-20 4:13 ` syzbot
2026-01-20 12:00 ` Jens Axboe
2026-01-20 13:07 ` syzbot
2026-01-20 13:35 ` Jens Axboe
2026-01-20 13:37 ` syzbot
2026-01-20 15:04 ` Jens Axboe
2026-01-20 18:05 ` Jens Axboe
2026-01-20 18:31 ` syzbot
2026-01-21 17:39 ` Jens Axboe
2026-01-21 17:41 ` Jens Axboe
2026-01-21 19:30 ` syzbot
2026-01-21 21:41 ` Jens Axboe
2026-01-21 21:43 ` 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=69718e02.050a0220.706b.0020.GAE@google.com \
--to=syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--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