From: Rong Chen <rong.a.chen@intel.com>
To: Jan Stancek <jstancek@redhat.com>, Ian Kent <raven@themaw.net>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, lkp@lists.01.org, ltp@lists.linux.it,
DavidHowells <dhowells@redhat.com>,
AlViro <viro@ZenIV.linux.org.uk>
Subject: Re: [LTP] [xfs] 73e5fff98b: kmsg.dev/zero:Can't_open_blockdev
Date: Thu, 14 Nov 2019 08:44:01 +0800 [thread overview]
Message-ID: <d0db75cc-440d-6de8-f6d2-ddf399a3bdb7@intel.com> (raw)
In-Reply-To: <975334005.11814790.1573625805426.JavaMail.zimbra@redhat.com>
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
prev parent reply other threads:[~2019-11-14 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 1:00 [xfs] 73e5fff98b: kmsg.dev/zero:Can't_open_blockdev kernel test robot
2019-11-12 8:39 ` Ian Kent
2019-11-12 12:02 ` [LTP] " Jan Stancek
2019-11-12 12:08 ` Christoph Hellwig
2019-11-13 1:13 ` Ian Kent
2019-11-13 6:04 ` Ian Kent
2019-11-13 6:16 ` Jan Stancek
2019-11-14 0:44 ` Rong Chen [this message]
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=d0db75cc-440d-6de8-f6d2-ddf399a3bdb7@intel.com \
--to=rong.a.chen@intel.com \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).