From: Jan Stancek <jstancek@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: kernel test robot <rong.a.chen@intel.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, lkp@lists.01.org,
Christoph Hellwig <hch@lst.de>,
ltp@lists.linux.it
Subject: Re: [LTP] [xfs] 73e5fff98b: kmsg.dev/zero:Can't_open_blockdev
Date: Tue, 12 Nov 2019 07:02:23 -0500 (EST) [thread overview]
Message-ID: <1108442397.11662343.1573560143066.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <3fb8b1b04dd7808b45caf5262ee629c09c71e0b6.camel@themaw.net>
----- Original Message -----
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <rong.a.chen@intel.com>
> >
> > [ 135.976643] LTP: starting fs_fill
> > [ 135.993912] /dev/zero: Can't open blockdev
>
> I've looked at the github source but I don't see how to find out what
> command was used when this error occurred so I don't know even how to
> start to work out what might have caused this.
>
> Can you help me to find the test script source please.
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/fs/fs_fill/fs_fill.c
Setup of that test is trying different file system types, and it looks
at errno code of "mount -t $fs /dev/zero /mnt/$fs".
Test still PASSes. This report appears to be only about extra message in dmesg,
which wasn't there before:
# mount -t xfs /dev/zero /mnt/xfs
# dmesg -c
[ 897.177168] /dev/zero: Can't open blockdev
Regards,
Jan
next prev parent reply other threads:[~2019-11-12 12:02 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 ` Jan Stancek [this message]
2019-11-12 12:08 ` [LTP] " 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
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=1108442397.11662343.1573560143066.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--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=rong.a.chen@intel.com \
/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).