From: Laurence Oberman <loberman@redhat.com>
To: linux-scsi@vger.kernel.org, "Martin K . Petersen" <mkp@kernel.org>
Cc: "James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
Hannes Reinecke <hare@suse.de>,
Bart Van Assche <bvanassche@acm.org>,
Wenchao Hao <haowenchao22@gmail.com>,
Wenchao Hao <haowenchao2@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Ming Lei <tom.leiming@gmail.com>, Will Deacon <will@kernel.org>,
cki-project@redhat.com, jmoyer@redhat.com, bgoncalv@redhat.com,
mpatalan@redhat.com, ftjahjad@redhat.com, fsuba@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] scsi: scsi_debug: Wait for async target cleanup on module exit
Date: Tue, 3 Nov 2026 14:32:35 -0500 [thread overview]
Message-ID: <20261103193235.1564898-3-loberman@redhat.com> (raw)
In-Reply-To: <20261103193235.1564898-1-loberman@redhat.com>
sdebug_target_destroy() is called with the host lock held, so it defers
removal of the per-target debugfs directory to
sdebug_tartget_cleanup_async() on sdebug_async_domain.
scsi_debug_exit() removes the hosts and then removes
sdebug_debugfs_root without waiting for that work. The recursive
removal of the root frees the per-target dentries, and a cleanup that
runs afterwards calls debugfs_remove() on a stale dentry:
BUG: KASAN: slab-use-after-free in _raw_spin_lock+0x2d/0x40
Workqueue: async async_run_entry_fn
Call Trace:
kasan_report+0x92/0xc0
_raw_spin_lock+0x2d/0x40
lockref_get+0x9/0x40
__simple_recursive_removal+0x35/0x570
debugfs_remove+0x40/0x60
sdebug_tartget_cleanup_async+0x43/0x60 [scsi_debug]
async_run_entry_fn+0x96/0x520
process_one_work+0x925/0x1910
worker_thread+0x567/0xcc0
kthread+0x355/0x450
Allocated by task 150:
__d_alloc+0x34/0x9e0
d_alloc+0x44/0x1d0
...
debugfs_create_dir+0x18/0x3d0
sdebug_target_alloc
scsi_alloc_target+0x7c7/0xa70
followed by a NULL inode dereference in down_write() from
__simple_recursive_removal(). CKI hit this running blktests throtl/001
on arm64. The cleanup can also run after the module text has been
freed.
Commit b402a0dce64a ("scsi: scsi_debug: Fix create target debugfs
failure") drains sdebug_async_domain before creating a target. Do the
same in scsi_debug_exit() just before removing the debugfs root, after
the driver has been unregistered so that no host can still be bound and
queue further cleanup work.
Fixes: f084fe52c640 ("scsi: scsi_debug: Add debugfs interface to fail target reset")
Reported-by: Catalin Marinas <catalin.marinas@arm.com>
Closes: https://lore.kernel.org/r/auja2VnJTp-ijxqu@arm.com
Reported-by: CKI Project <cki-project@redhat.com>
Closes: https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:3017229113
Signed-off-by: Laurence Oberman <loberman@redhat.com>
---
drivers/scsi/scsi_debug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
index a922c8318a2f..deaed8b3e6c4 100644
--- a/drivers/scsi/scsi_debug.c
+++ b/drivers/scsi/scsi_debug.c
@@ -9053,6 +9053,8 @@ static void __exit scsi_debug_exit(void)
sdebug_erase_all_stores(false);
xa_destroy(per_store_ap);
+ /* Wait for deferred per-target debugfs cleanup before removing the root */
+ async_synchronize_full_domain(&sdebug_async_domain);
debugfs_remove(sdebug_debugfs_root);
}
--
2.56.0
next prev parent reply other threads:[~2026-11-03 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e4ba1820a7c56867bf7fff07bd52ff3f79573a1.camel@redhat.com>
2026-11-03 19:32 ` [PATCH 0/2] scsi: fix scsi_debug module-exit panic and pseudo target leak Laurence Oberman
2026-11-03 19:32 ` [PATCH 1/2] scsi: core: Fix target reap_ref leak in scsi_get_pseudo_sdev() Laurence Oberman
2026-11-03 19:32 ` Laurence Oberman [this message]
2026-11-03 20:53 ` [PATCH] scsi: scsi_debug: Wait for async target cleanup on module exit Laurence Oberman
2026-11-03 20:52 ` [PATCH 2/2] " Laurence Oberman
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=20261103193235.1564898-3-loberman@redhat.com \
--to=loberman@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bgoncalv@redhat.com \
--cc=bvanassche@acm.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=fsuba@redhat.com \
--cc=ftjahjad@redhat.com \
--cc=haowenchao22@gmail.com \
--cc=haowenchao2@huawei.com \
--cc=hare@suse.de \
--cc=jmoyer@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=mpatalan@redhat.com \
--cc=tom.leiming@gmail.com \
--cc=will@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
all inboxes | Powered by JetHome®