public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"mcgrof@kernel.org" <mcgrof@kernel.org>,
	"sw.prabhu6@gmail.com" <sw.prabhu6@gmail.com>,
	Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH blktests v5 2/4] srp/rc: replace module removal with patient module removal
Date: Sat, 10 Jan 2026 06:08:57 +0000	[thread overview]
Message-ID: <aWHrykwwVlyGRSfC@shinmob> (raw)
In-Reply-To: <435451b8-4d54-4306-b29c-819a55b6b5f1@acm.org>

On Dec 26, 2025 / 10:08, Bart Van Assche wrote:
> On 12/25/25 1:09 PM, Shin'ichiro Kawasaki wrote:
> > Suggested-by: Bart Van Assche <bvanassche@acm.org>
> 
> I can't remember that I suggested to use _patient_rmmod. Luis, can you
> provide a link that shows that I suggested to use _patient_rmmod for the
> SRP tests? If not, please leave out the Suggested-by tag.

Based on your another comment below, I think this patch can be dropped. If this
is the case, no need to worry about the Suggested-by tag.

> 
> > diff --git a/tests/srp/rc b/tests/srp/rc
> > index 47b9546..2d3d615 100755
> > --- a/tests/srp/rc
> > +++ b/tests/srp/rc
> > @@ -331,19 +331,10 @@ start_srp_ini() {
> >   # Unload the SRP initiator driver.
> >   stop_srp_ini() {
> > -	local i
> > -
> >   	log_out
> > -	for ((i=40;i>=0;i--)); do
> > -		remove_mpath_devs || return $?
> > -		_unload_module ib_srp >/dev/null 2>&1 && break
> > -		sleep 1
> > -	done
> > -	if [ -e /sys/module/ib_srp ]; then
> > -		echo "Error: unloading kernel module ib_srp failed"
> > -		return 1
> > -	fi
> > -	_unload_module scsi_transport_srp || return $?
> > +	remove_mpath_devs || return $?
> > +	_patient_rmmod ib_srp || return 1
> > +	_patient_rmmod scsi_transport_srp || return $?
> >   }
> 
> The loop should be around both remove_mpath_devs and _unload_module
> because multipathd may add new paths concurrently with the for-loop.
> Please back out the above changes from this patch.

I see. If we back out the changes above, this patch does not have much
meaning. Just replacing the _unload_module calls with _patient_rmmod calls. I
will drop this patch in the next spin. In stead, I will modify the first patch
to replace all of _unload_module calls in srp/rc with _patient_rmmod calls.

  reply	other threads:[~2026-01-10  6:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25 12:09 [PATCH blktests v5 0/4] replace module removal with patient module removal Shin'ichiro Kawasaki
2025-12-25 12:09 ` [PATCH blktests v5 1/4] check,common/*: " Shin'ichiro Kawasaki
2025-12-25 12:09 ` [PATCH blktests v5 2/4] srp/rc: " Shin'ichiro Kawasaki
2025-12-26  9:08   ` Bart Van Assche
2026-01-10  6:08     ` Shinichiro Kawasaki [this message]
2025-12-25 12:09 ` [PATCH blktests v5 3/4] check: reimplement _unload_modules() with _patient_rmmod() Shin'ichiro Kawasaki
2025-12-25 12:09 ` [PATCH blktests v5 4/4] check: check reference count for modprobe --remove --wait success case Shin'ichiro Kawasaki

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=aWHrykwwVlyGRSfC@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox