From: "Martin K. Petersen" <mkp@kernel.org>
To: Giuseppe Piscitelli <ooonea@gmail.com>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: scsi_debug: Drain target cleanup before module exit
Date: Wed, 28 Oct 2026 21:23:13 -0400 [thread overview]
Message-ID: <yq133tp5mh5.fsf@mail.kernel.org> (raw)
In-Reply-To: <20261026202342.668361-1-ooonea@gmail.com>
Giuseppe,
> Target destruction queues cleanup in an exclusive async domain. The
> module loader's async_synchronize_full() does not wait for exclusive
> domains. Wait for target cleanup after removing the hosts and before
> removing the debugfs root and returning from module exit.
Applied to 7.4/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-10-29 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 20:23 [PATCH] scsi: scsi_debug: Drain target cleanup before module exit Giuseppe Piscitelli
2026-10-29 1:23 ` Martin K. Petersen [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=yq133tp5mh5.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ooonea@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