From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <tom.leiming@gmail.com>
Cc: io-uring <io-uring@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Liam R. Howlett" <liam.howlett@oracle.com>
Subject: RCU warning off ublk_buf_cleanup() -> mas_for_each()
Date: Tue, 21 Apr 2026 11:47:31 -0600 [thread overview]
Message-ID: <0349d72d-dff8-4f9f-b448-919fa5ae96da@kernel.dk> (raw)
Hi Ming,
Ran into the below running tests on the current tree:
=============================
WARNING: suspicious RCU usage
7.0.0+ #16 Tainted: G N
-----------------------------
lib/maple_tree.c:759 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by iou-wrk-55535/55536:
#0: ffff800085a451a0 (ublk_ctl_mutex){+.+.}-{4:4}, at: ublk_ctrl_del_dev+0xdc/0x2f8
stack backtrace:
CPU: 4 UID: 0 PID: 55536 Comm: iou-wrk-55535 Tainted: G N 7.0.0+ #16 PREEMPT
Tainted: [N]=TEST
Hardware name: linux,dummy-virt (DT)
Call trace:
show_stack+0x1c/0x30 (C)
dump_stack_lvl+0x68/0x90
dump_stack+0x18/0x20
lockdep_rcu_suspicious+0x170/0x200
mas_walk+0x3f0/0x6a0
mas_find+0x1b4/0x6b0
ublk_buf_cleanup+0xe0/0x240
ublk_cdev_rel+0x34/0x1b0
device_release+0xa4/0x350
kobject_put+0x138/0x250
put_device+0x18/0x30
ublk_put_device+0x18/0x28
ublk_ctrl_del_dev+0x120/0x2f8
ublk_ctrl_uring_cmd+0x598/0x29b8
io_uring_cmd+0x1e0/0x468
__io_issue_sqe+0xa4/0x748
io_issue_sqe+0x80/0xf68
io_wq_submit_work+0x26c/0xdc8
io_worker_handle_work+0x334/0xf20
io_wq_worker+0x278/0x9e8
ret_from_fork+0x10/0x20
Buffer I/O error on dev ublkb0, logical block 0, async page read
Buffer I/O error on dev ublkb0, logical block 0, async page read
ublkb0: unable to read partition table
Buffer I/O error on dev ublkb0, logical block 0, async page read
Buffer I/O error on dev ublkb0, logical block 0, async page read
Buffer I/O error on dev ublkb0, logical block 512, async page read
Buffer I/O error on dev ublkb0, logical block 512, async page read
Buffer I/O error on dev ublkb0, logical block 0, async page read
Buffer I/O error on dev ublkb0, logical block 512, async page read
and I briefly looked at it, but then just gave up as a) the maple tree
documentation is not that detailed, and b) other in-tree users also just
call mas_for_each() without either a lock held or RCU read side locked.
Adding Liam for shedding some light on this...
--
Jens Axboe
next reply other threads:[~2026-04-21 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 17:47 Jens Axboe [this message]
2026-04-21 18:04 ` RCU warning off ublk_buf_cleanup() -> mas_for_each() Jens Axboe
2026-04-21 20:28 ` Liam R. Howlett
2026-04-21 21:41 ` Jens Axboe
2026-04-21 21:56 ` Liam R. Howlett
2026-04-21 22:03 ` Jens Axboe
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=0349d72d-dff8-4f9f-b448-919fa5ae96da@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=liam.howlett@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=tom.leiming@gmail.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