From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH blktests] nvme: add dh module requirement for tests that involve dh groups
Date: Wed, 31 Aug 2022 04:59:46 +0000 [thread overview]
Message-ID: <20220831045946.3elujhdydvqkkhv4@shindev> (raw)
In-Reply-To: <a5c3c8e7-4b0a-9930-8f90-e534d2a82bdf@grimberg.me>
On Aug 30, 2022 / 16:26, Sagi Grimberg wrote:
[...]
> > Unfortunately, your patch does not avoid the failure after the recent commit
> > 06a0ba866d90 ("common/rc: avoid module load in _have_driver()"). As the commit
> > title says, _have_driver no longer has the side-effect to leave the dh_generic
> > module loaded. Instead, I suggest to load dh_generic in the test() function:
> >
> > diff --git a/tests/nvme/043 b/tests/nvme/043
> > index 381ae75..dbe9d3f 100755
> > --- a/tests/nvme/043
> > +++ b/tests/nvme/043
> > @@ -40,6 +40,8 @@ test() {
> >
> > _setup_nvmet
> >
> > + modprobe -q dh_generic
> > +
> > truncate -s 512M "${file_path}"
> >
> > _create_nvmet_subsystem "${subsys_name}" "${file_path}"
> > @@ -88,5 +90,7 @@ test() {
> >
> > rm "${file_path}"
> >
> > + modprobe -qr dh_generic
> > +
> > echo "Test complete"
> > }
> >
>
> That's fine with me, can you prepare an alternative patch for it?
Sure, will post it soon.
--
Shin'ichiro Kawasaki
next prev parent reply other threads:[~2022-08-31 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 8:36 [PATCH blktests] nvme: add dh module requirement for tests that involve dh groups Sagi Grimberg
2022-08-30 4:46 ` Shinichiro Kawasaki
2022-08-30 7:05 ` Sagi Grimberg
2022-08-30 7:13 ` Jackie Liu
2022-08-30 7:37 ` Sagi Grimberg
2022-08-30 7:44 ` Jackie Liu
2022-08-30 10:23 ` Shinichiro Kawasaki
2022-08-30 13:26 ` Sagi Grimberg
2022-08-31 4:59 ` Shinichiro Kawasaki [this message]
2022-09-09 4:14 ` 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=20220831045946.3elujhdydvqkkhv4@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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