public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
	shinichiro.kawasaki@wdc.com, linux-block@vger.kernel.org
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH blktests] nvme/068: add a test for multipath delayed removal
Date: Thu, 16 Apr 2026 12:45:31 +0100	[thread overview]
Message-ID: <cdad65b5-8ba5-46f9-aee1-8a5b5467be4c@oracle.com> (raw)
In-Reply-To: <c1e9d3b5-c236-4e5c-8cf2-90df5e32005b@linux.ibm.com>

On 16/04/2026 12:18, Nilay Shroff wrote:
> 
>> diff --git a/tests/nvme/068 b/tests/nvme/068
>> new file mode 100644
>> index 0000000..e06fd6b
>> --- /dev/null
>> +++ b/tests/nvme/068
>> @@ -0,0 +1,118 @@
>> +#!/bin/bash
>> +# SPDX-License-Identifier: GPL-3.0+
>> +# Copyright (C) 2026 John Garry
>> +#
>> +# Test NVMe multipath delayed removal works as expected
>> +
> Should we also reference the commit 62188639ec16 ("nvme-multipath:
> introduce delayed removal of the multipath head node") which introduced
> this feature in the kernel?
> 

Sure, if you think that it is useful.

We could also introduce at some point the _fixed_by_kernel_commit (like 
xfstests), but I am not sure if it has value for blktests

>> +. tests/nvme/rc
>> +. common/xfs
>> +
>> +DESCRIPTION="NVMe multipath delayed removal test"
>> +QUICK=1
>> +
>> +requires() {
>> +    _nvme_requires
>> +    _have_loop
>> +    _have_module_param_value nvme_core multipath Y
>> +    _require_nvme_trtype_is_fabrics
>> +}
>> +
>> +set_conditions() {
>> +    _set_nvme_trtype "$@"
>> +}
>> +
>> +_delayed_nvme_reconnect_ctrl() {
>> +    sleep 5
>> +    _nvme_connect_subsys
>> +}
>> +
>> +test() {
>> +    echo "Running ${TEST_NAME}"
>> +
>> +    _setup_nvmet
>> +
>> +    local nvmedev
>> +    local ns
>> +    local bytes_written
>> +    local refcnt_orig
>> +    local refcnt
>> +    _nvmet_target_setup
>> +
>> +    _nvme_connect_subsys
>> +
>> +    # Part a: Prove that writes fail when no path returns. Any reads or
>> +    #      writes are queued during the delayed removal period. If no
>> +    #      paths return before the timer expires, then those IOs should
>> +    #      fail.
>> +    #      During the delayed removal period, ensure that the module
>> +    #      refcnt is incremented, to prove that we cannot remove the
>> +    #      driver during this period.
>> +    nvmedev=$(_find_nvme_dev "${def_subsysnqn}")
>> +    ns=$(_find_nvme_ns "${def_subsys_uuid}")
>> +    refcnt=$(_module_use_count nvme_core)
> 
> Should the refcount be stored in $refcnt_orig instead of $refcnt?

Yeah, that's a small bug, as I needlessly store it twice:

+	refcnt=$(_module_use_count nvme_core)
+	echo 10 > "/sys/block/"$ns"/delayed_removal_secs"
+	refcnt_orig=$(_module_use_count nvme_core)

> 
>> +    echo 10 > "/sys/block/"$ns"/delayed_removal_secs"
>> +    refcnt_orig=$(_module_use_count nvme_core)
> 
> We may not need to again store refcnt here if we store it
> before enabling delayed_removal_sec above.
> 
> Other than above trivial comments, this looks good to me.
> 

Cheers,
John


  reply	other threads:[~2026-04-16 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 10:41 [PATCH blktests] nvme/068: add a test for multipath delayed removal John Garry
2026-04-15 17:58 ` Chaitanya Kulkarni
2026-04-16 11:18 ` Nilay Shroff
2026-04-16 11:45   ` John Garry [this message]
2026-04-16 12:50 ` Shinichiro Kawasaki
2026-04-16 13:03   ` John Garry
2026-04-17  2:22     ` Shinichiro 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=cdad65b5-8ba5-46f9-aee1-8a5b5467be4c@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.com \
    --cc=shinichiro.kawasaki@wdc.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