[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <avghd7jgrqgh4pgewihhoa7dm3b7eb4oe3u2clcbefirevikdz@jo6cyhwfsn6y>
Date: Sun, 30 Apr 2023 10:08:48 +0000
From: Shinichiro Kawasaki <shinichiro.kawasaki@....com>
To: Daniel Wagner <dwagner@...e.de>
CC: Chaitanya Kulkarni <chaitanyak@...dia.com>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Shin'ichiro Kawasaki <shinichiro@...tmail.com>
Subject: Re: [PATCH blktests v2 2/2] nvme-rc: Cleanup fc resource before
module unloading
On Apr 19, 2023 / 12:36, Daniel Wagner wrote:
> On Wed, Apr 19, 2023 at 09:41:28AM +0000, Chaitanya Kulkarni wrote:
> > were you able to test this with RDMA ?
>
> Yes, I've tested it with all transports (loop, tcp, rdma, fc)
>
> > just want to make sure we are not breaking anything since we are changing
> > the order of module unload and stop_soft_rdma() in this patch ...
>
> Sure thing
I also tested, and observed no result change by these two patches. Only one
failure I observed is nvme/003 due to lockdep WARN, but it happens regardless
of the patches.
Powered by blists - more mailing lists