[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR04MB57494AD6FADC0654403613CE86B30@BYAPR04MB5749.namprd04.prod.outlook.com>
Date: Fri, 13 Sep 2019 22:37:23 +0000
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
To: Bart Van Assche <bvanassche@....org>,
André Almeida <andrealmeid@...labora.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "corbet@....net" <corbet@....net>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"kernel@...labora.com" <kernel@...labora.com>,
"krisman@...labora.com" <krisman@...labora.com>
Subject: Re: [PATCH v2 1/4] null_blk: do not fail the module load with zero
devices
On 09/13/2019 03:18 PM, Bart Van Assche wrote:
> I just noticed that this patch is necessary to unbreak blktests. The srp
> tests fail as follows with Jens' for-next branch:
>
> modprobe: ERROR: could not insert 'null_blk': Invalid argument
>
> I think that error is triggered by the following statement in
> common/multipath-over-rdma:
>
> modprobe null_blk nr_devices=0 || return $?
>
> Bart.
>
Not only that I'm sure my membacked null_blk testcases will also start
failing without this patch, which I've not posted on mailing list yet.
Powered by blists - more mailing lists