[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d0db75cc-440d-6de8-f6d2-ddf399a3bdb7@intel.com>
Date: Thu, 14 Nov 2019 08:44:01 +0800
From: Rong Chen <rong.a.chen@...el.com>
To: Jan Stancek <jstancek@...hat.com>, Ian Kent <raven@...maw.net>
Cc: Christoph Hellwig <hch@....de>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
LKML <linux-kernel@...r.kernel.org>, linux-xfs@...r.kernel.org,
lkp@...ts.01.org, ltp@...ts.linux.it,
DavidHowells <dhowells@...hat.com>,
AlViro <viro@...IV.linux.org.uk>
Subject: Re: [LTP] [xfs] 73e5fff98b: kmsg.dev/zero:Can't_open_blockdev
On 11/13/19 2:16 PM, Jan Stancek wrote:
>
> ----- Original Message -----
>>>>> # mount -t xfs /dev/zero /mnt/xfs
>>> Assuming that is what is being done ...
>> Arrrh, of course, a difference between get_tree_bdev() and
>> mount_bdev() is that get_tree_bdev() prints this message when
>> blkdev_get_by_path() fails whereas mount_bdev() doesn't.
>>
>> Both however do return an error in this case so the behaviour
>> is the same.
>>
>> So I'm calling this not a problem with the subject patch.
>>
>> What needs to be done to resolve this in ltp I don't know?
> I think that's question for kernel test robot, which has this extra
> check built on top. ltp itself doesn't treat this extra message as FAIL.
>
> Jan
>
Hi all,
Thanks for your help, kernel test robot bisected automatically for new
error:
kern :err : [ 135.993912] /dev/zero: Can't open blockdev
Please ignore the report if it's not a problem.
Best Regards,
Rong Chen
Powered by blists - more mailing lists