[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <975334005.11814790.1573625805426.JavaMail.zimbra@redhat.com>
Date: Wed, 13 Nov 2019 01:16:45 -0500 (EST)
From: Jan Stancek <jstancek@...hat.com>
To: Ian Kent <raven@...maw.net>,
kernel test robot <rong.a.chen@...el.com>
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
----- 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
Powered by blists - more mailing lists