From: Jens Axboe <axboe@kernel.dk>
To: lkp@lists.01.org
Subject: Re: [null_blk] f2298c0403b:
Date: Wed, 07 Jan 2015 08:24:08 -0700 [thread overview]
Message-ID: <54AD4F98.6070702@kernel.dk> (raw)
In-Reply-To: <1420598028.6201.70.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On 01/06/2015 07:33 PM, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> commit f2298c0403b0dfcaef637eba0c02c4a06d7a25ab ("null_blk: multi queue aware block test driver")
>
>
> testbox/testcase/testparams: vm-kbuild-yocto-i386/boot/1
>
> 320ae51feed5c2f1 f2298c0403b0dfcaef637eba0c
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> :10 100% 10:10 kmsg.VFS:could_not_find_a_valid_V7_on_nullb1
> :10 100% 10:10 kmsg.VFS:could_not_find_a_valid_V7_on_nullb0
> 1:10 -10% :10 kmsg.vm86_32:could_not_access_userspace_vm86_info
>
> vm-kbuild-yocto-i386: qemu-system-i386 -enable-kvm
> Memory: 320M
>
> [ 1.971241] mtip32xx Version 1.2.6os3
> [ 1.971311] blk-mq: CPU -> queue map
> [ 1.971312] CPU 0 -> Queue 0
> [ 1.971314] CPU 1 -> Queue 0
> [ 1.971628] nullb0: unknown partition table
> [ 1.971748] blk-mq: CPU -> queue map
> [ 1.971749] CPU 0 -> Queue 0
> [ 1.971751] CPU 1 -> Queue 0
> [ 1.972023] nullb1: unknown partition table
> [ 1.972096] null: module loaded
> [ 1.972131] ibmasm: IBM ASM Service Processor Driver version 1.0 loaded
>
> I think this is at least confusing for the end user.
Sorry, not sure I follow at all. If you're expecting the null block
driver to actually store data, then yes, you are going to have a bad
time. It's a test tool for storage stack development.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [null_blk] f2298c0403b:
Date: Wed, 07 Jan 2015 08:24:08 -0700 [thread overview]
Message-ID: <54AD4F98.6070702@kernel.dk> (raw)
In-Reply-To: <1420598028.6201.70.camel@intel.com>
On 01/06/2015 07:33 PM, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> commit f2298c0403b0dfcaef637eba0c02c4a06d7a25ab ("null_blk: multi queue aware block test driver")
>
>
> testbox/testcase/testparams: vm-kbuild-yocto-i386/boot/1
>
> 320ae51feed5c2f1 f2298c0403b0dfcaef637eba0c
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> :10 100% 10:10 kmsg.VFS:could_not_find_a_valid_V7_on_nullb1
> :10 100% 10:10 kmsg.VFS:could_not_find_a_valid_V7_on_nullb0
> 1:10 -10% :10 kmsg.vm86_32:could_not_access_userspace_vm86_info
>
> vm-kbuild-yocto-i386: qemu-system-i386 -enable-kvm
> Memory: 320M
>
> [ 1.971241] mtip32xx Version 1.2.6os3
> [ 1.971311] blk-mq: CPU -> queue map
> [ 1.971312] CPU 0 -> Queue 0
> [ 1.971314] CPU 1 -> Queue 0
> [ 1.971628] nullb0: unknown partition table
> [ 1.971748] blk-mq: CPU -> queue map
> [ 1.971749] CPU 0 -> Queue 0
> [ 1.971751] CPU 1 -> Queue 0
> [ 1.972023] nullb1: unknown partition table
> [ 1.972096] null: module loaded
> [ 1.972131] ibmasm: IBM ASM Service Processor Driver version 1.0 loaded
>
> I think this is at least confusing for the end user.
Sorry, not sure I follow at all. If you're expecting the null block
driver to actually store data, then yes, you are going to have a bad
time. It's a test tool for storage stack development.
--
Jens Axboe
next prev parent reply other threads:[~2015-01-07 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 2:33 [null_blk] f2298c0403b: Huang Ying
2015-01-07 2:33 ` [LKP] " Huang Ying
2015-01-07 15:24 ` Jens Axboe [this message]
2015-01-07 15:24 ` Jens Axboe
2015-01-08 0:52 ` Huang Ying
2015-01-08 0:52 ` [LKP] " Huang Ying
2015-01-08 1:52 ` Ming Lei
2015-01-08 1:52 ` [LKP] " Ming Lei
2015-01-08 2:05 ` Huang Ying
2015-01-08 2:05 ` [LKP] " Huang Ying
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=54AD4F98.6070702@kernel.dk \
--to=axboe@kernel.dk \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.