From: syzbot <syzbot+a62ea1d07ee6ab5ec277@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [mm?] INFO: rcu detected stall in sys_io_uring_enter (3)
Date: Tue, 20 Jan 2026 07:11:43 -0800 [thread overview]
Message-ID: <696f9b2f.050a0220.4cb9c.001a.GAE@google.com> (raw)
In-Reply-To: <69456c14.a70a0220.207337.0115.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in sys_io_uring_enter (3)
Author: axboe@kernel.dk
#syz set subsystems: mm
Doesn't look like io_uring at all, it's pretty late in the trace when
this reproducer has already shit its pants.
prev parent reply other threads:[~2026-01-20 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 15:15 syzbot
2026-01-20 15:11 ` 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=696f9b2f.050a0220.4cb9c.001a.GAE@google.com \
--to=syzbot+a62ea1d07ee6ab5ec277@syzkaller.appspotmail.com \
--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
Powered by JetHome