All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+10a9b495f54a17b607a6@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hdanton@sina.com, io-uring@vger.kernel.org,
	 kbusch@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 17:15:03 -0700	[thread overview]
Message-ID: <69000b07.050a0220.32483.00cb.GAE@google.com> (raw)
In-Reply-To: <20251027222454.8795-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+10a9b495f54a17b607a6@syzkaller.appspotmail.com
Tested-by: syzbot+10a9b495f54a17b607a6@syzkaller.appspotmail.com

Tested on:

commit:         8fec172c Add linux-next specific files for 20251027
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=140bac92580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9da2d5fce59079e1
dashboard link: https://syzkaller.appspot.com/bug?extid=10a9b495f54a17b607a6
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=148753cd980000

Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2025-10-28  0:15 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
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 [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=69000b07.050a0220.32483.00cb.GAE@google.com \
    --to=syzbot+10a9b495f54a17b607a6@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hdanton@sina.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kbusch@kernel.org \
    --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 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.