From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+58928048fd1416f1457c@syzkaller.appspotmail.com>,
asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (4)
Date: Fri, 4 Apr 2025 16:27:03 -0600 [thread overview]
Message-ID: <7472b072-9c08-4e5a-8f16-8a56647ebc9a@kernel.dk> (raw)
In-Reply-To: <b51adba8-7722-4f74-a865-47bf1638820f@kernel.dk>
#syz test: git://git.kernel.dk/linux.git io_uring-6.15
--
Jens Axboe
next prev parent reply other threads:[~2025-04-04 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 22:17 [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (4) syzbot
2024-10-26 5:43 ` syzbot
2024-10-26 13:44 ` Jens Axboe
2024-10-27 0:07 ` Jens Axboe
2025-04-04 22:27 ` Jens Axboe [this message]
2025-04-04 22:54 ` syzbot
2025-04-05 11:46 ` Jens Axboe
2025-04-05 12:30 ` syzbot
2025-04-07 13:54 ` Jens Axboe
2025-04-07 14:25 ` 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=7472b072-9c08-4e5a-8f16-8a56647ebc9a@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+58928048fd1416f1457c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox