From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+33504742c13bcd6c9541@syzkaller.appspotmail.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] INFO: rcu detected stall in io_ring_exit_work (3)
Date: Tue, 20 Jan 2026 08:19:40 -0700 [thread overview]
Message-ID: <0a9e81e3-f77a-4607-872d-aa03e9680134@kernel.dk> (raw)
In-Reply-To: <6966b578.a70a0220.245e30.0004.GAE@google.com>
Doesn't look io_uring relevant at all, and I don't know where it should go:
#syz set subsystems: kernel
--
Jens Axboe
prev parent reply other threads:[~2026-01-20 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 21:13 [syzbot] [io-uring?] INFO: rcu detected stall in io_ring_exit_work (3) syzbot
2026-01-20 15:19 ` Jens Axboe [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=0a9e81e3-f77a-4607-872d-aa03e9680134@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+33504742c13bcd6c9541@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