public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Re: [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (6)
Date: Wed, 21 Jan 2026 15:26:51 -0800	[thread overview]
Message-ID: <697160bb.050a0220.706b.001a.GAE@google.com> (raw)
In-Reply-To: <68a2decc.050a0220.e29e5.0099.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [io-uring?] INFO: task hung in io_wq_put_and_exit (6)
Author: axboe@kernel.dk

On 1/20/26 8:04 AM, Jens Axboe wrote:
> Just to wrap this one up - there's a fairly lengthy explanation posted
> here:
> 
> https://lore.kernel.org/io-uring/937c3e38-368e-43eb-9d7e-2dcc0697799f@kernel.dk/
> 
> which details why this isn't really a bug, it's just slow exit due to
> the odd huge reads (and number of them) syzbot queues up with io_uring
> before exiting.

Another retry, hoping that syzbot has unborked itself again:

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git syztest

-- 
Jens Axboe


      parent reply	other threads:[~2026-01-21 23:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2026-01-21 23:26 ` syzbot [this message]

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=697160bb.050a0220.706b.001a.GAE@google.com \
    --to=syzbot+4eb282331cab6d5b6588@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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