From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ben Carey <benjamin.james.carey3@gmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] RCU hang with io_uring nvme polling
Date: Fri, 26 Jun 2026 10:05:23 -0600 [thread overview]
Message-ID: <aj6jQyJd3zmZFcwx@kbusch-mbp> (raw)
In-Reply-To: <85d1f999-7778-4c74-9d72-b8ac8500de31@kernel.dk>
On Fri, Jun 26, 2026 at 09:17:35AM -0600, Jens Axboe wrote:
> On 6/26/26 9:09 AM, Ben Carey wrote:
> > From a running QEMU image with the latest kernel:
> > 1. Attach GDB to the running instance.
> > 2. Enable io polling via sysfs (echo 1 > /sys/block/nvme0n1/queue/io_poll).
>
> That's not how that works at all. You need to setup poll queues on the
> nvme driver side, using the nvme.poll_queues=XX kernel parameter, or if
> using nvme as a module, load the module with poll_queues=XX where XX is
> the number of poll queues. You're not doing any polled IO as-is, and the
> above should also have dumped a dmesg message about how that does
> absolutely nothing.
>
> That said, it should still work, just not doing polled IO. I'll take a
> look sometime next week, OOO right now.
Yeah, the sysfs attribute does nothing, but Ben mentioned they had the
correct kernel command line:
BOOT_IMAGE=/vmlinuz-7.1.0-g3996771b8f75 root=/dev/mapper/ubuntu--vg-ubuntu--lv \
ro nvme.poll_queues=1 nokaslr
So they did enable polling, but the "echo" step is just confusing and
unnecessary.
I tried out the test, and there does appear to be a problem here, so I'm
looking into it.
next prev parent reply other threads:[~2026-06-26 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:09 [BUG] RCU hang with io_uring nvme polling Ben Carey
2026-06-26 15:17 ` Jens Axboe
2026-06-26 16:05 ` Keith Busch [this message]
2026-06-26 16:06 ` Jens Axboe
2026-06-26 16:33 ` Keith Busch
2026-06-26 16:35 ` Jens Axboe
2026-06-26 16:48 ` Keith Busch
[not found] ` <CA+KFGSoyCSRzgamm-38oyAtEsqd7wZZ8awL79P40x7a819EK4w@mail.gmail.com>
2026-06-26 17:41 ` Ben Carey
2026-07-03 17:20 ` Ben Carey
2026-07-04 17:01 ` Keith Busch
2026-07-04 19:35 ` Ben Carey
2026-07-04 19:38 ` Ben Carey
2026-07-08 13:35 ` Keith Busch
2026-06-29 20:47 ` Ben Carey
2026-06-29 21:40 ` Keith Busch
2026-06-29 22:04 ` Keith Busch
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=aj6jQyJd3zmZFcwx@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=benjamin.james.carey3@gmail.com \
--cc=io-uring@vger.kernel.org \
--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