From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: syzbot <syzbot+10a9b495f54a17b607a6@syzkaller.appspotmail.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_uring_del_tctx_node (5)
Date: Mon, 27 Oct 2025 16:57:52 -0600 [thread overview]
Message-ID: <aP_48DOFFdm4kB7Q@kbusch-mbp> (raw)
In-Reply-To: <d0cd8a65-b565-4275-b87d-51d10e88069f@kernel.dk>
On Mon, Oct 27, 2025 at 04:04:05PM -0600, Jens Axboe wrote:
>
> commit 1cba30bf9fdd6c982708f3587f609a30c370d889
> Author: Keith Busch <kbusch@kernel.org>
> Date: Thu Oct 16 11:09:38 2025 -0700
>
> io_uring: add support for IORING_SETUP_SQE_MIXED
>
> leaves fdinfo open up to being broken. Before, we had:
>
> sq_entries = min(sq_tail - sq_head, ctx->sq_entries);
>
> as a cap for the loop, now you just have:
>
> while (sq_head < sq_tail) {
>
> which seems like a bad idea. It's also missing an sq_head increment if
> we hit this condition:
This would have to mean the application did an invalid head ring-wrap,
right? Regardless, I messed up and the wrong thing will happen here in
that case as well as the one you mentioned.
next prev parent reply other threads:[~2025-10-27 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 21:07 [syzbot] [io-uring?] INFO: task hung in io_uring_del_tctx_node (5) syzbot
2025-10-27 22:04 ` Jens Axboe
2025-10-27 22:57 ` Keith Busch [this message]
2025-10-27 23:15 ` Jens Axboe
2025-10-28 0:03 ` Keith Busch
2025-10-28 1:09 ` Jens Axboe
2025-10-27 22:24 ` Hillf Danton
2025-10-28 0:15 ` 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=aP_48DOFFdm4kB7Q@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+10a9b495f54a17b607a6@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 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.