From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "mcgrof@kernel.org" <mcgrof@kernel.org>,
"sw.prabhu6@gmail.com" <sw.prabhu6@gmail.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH blktests v7 0/3] replace module removal with patient module removal
Date: Wed, 21 Jan 2026 02:22:00 +0000 [thread overview]
Message-ID: <aXA4ElGLfsfv06C6@shinmob> (raw)
In-Reply-To: <20260115091101.70464-1-shinichiro.kawasaki@wdc.com>
On Jan 15, 2026 / 18:10, Shin'ichiro Kawasaki wrote:
> This patch series was originally authored by Luis Chamberlain [0][1]. I
> reworked and post it as this series.
>
> [0] https://lore.kernel.org/all/20221220235324.1445248-2-mcgrof@kernel.org/T/#u
> [1] https://lore.kernel.org/linux-block/20251126171102.3663957-1-mcgrof@kernel.org/
>
> Original cover letter:
>
> We now have the modprobe --wait upstream so use that if available.
>
> The patient module remover addresses race conditions where module removal
> can fail due to userspace temporarily bumping the refcount (e.g., via
> blkdev_open() calls). If your version of kmod supports modprobe --wait,
> we use that. Otherwise we implement our own patient module remover.
FYI, I applied this series. Thanks for the contribution and the reviews!
prev parent reply other threads:[~2026-01-21 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:10 [PATCH blktests v7 0/3] replace module removal with patient module removal Shin'ichiro Kawasaki
2026-01-15 9:10 ` [PATCH blktests v7 1/3] check,common,srp/rc: " Shin'ichiro Kawasaki
2026-01-15 9:11 ` [PATCH blktests v7 2/3] check: reimplement _unload_modules() with _patient_rmmod() Shin'ichiro Kawasaki
2026-01-15 9:11 ` [PATCH blktests v7 3/3] check: check reference count for modprobe --remove --wait success case Shin'ichiro Kawasaki
2026-01-19 10:01 ` [PATCH blktests v7 0/3] replace module removal with patient module removal Daniel Wagner
2026-01-20 17:33 ` Bart Van Assche
2026-01-21 2:22 ` Shinichiro Kawasaki [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=aXA4ElGLfsfv06C6@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=bvanassche@acm.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sw.prabhu6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.