From: Huang Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [null_blk] f2298c0403b:
Date: Thu, 08 Jan 2015 10:05:01 +0800 [thread overview]
Message-ID: <1420682701.6201.79.camel@intel.com> (raw)
In-Reply-To: <CACVXFVPcRrKR36WpGxjcLUQAqLYbFmM-6uyavgFVA8PaZRFsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
On Thu, 2015-01-08 at 09:52 +0800, Ming Lei wrote:
> On Thu, Jan 8, 2015 at 8:52 AM, Huang Ying <ying.huang@intel.com> wrote:
> > On Wed, 2015-01-07 at 08:24 -0700, Jens Axboe wrote:
> >> 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.
> >
> > I understand that null block is just for testing.
> >
> > I just think the message like:
> >
> > [ 1.971628] nullb0: unknown partition table
> >
> > may confuse the end user. They may think there are something wrong.
> > But it is not. Is there any way to suppress this?
>
> It can be logged for any normal block devices which have not be
> partitioned, and users should have understood that, IMO.
Then it is OK. Thanks for explanation.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: Huang Ying <ying.huang@intel.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, LKML <linux-kernel@vger.kernel.org>,
LKP ML <lkp@01.org>
Subject: Re: [LKP] [null_blk] f2298c0403b:
Date: Thu, 08 Jan 2015 10:05:01 +0800 [thread overview]
Message-ID: <1420682701.6201.79.camel@intel.com> (raw)
In-Reply-To: <CACVXFVPcRrKR36WpGxjcLUQAqLYbFmM-6uyavgFVA8PaZRFsFQ@mail.gmail.com>
On Thu, 2015-01-08 at 09:52 +0800, Ming Lei wrote:
> On Thu, Jan 8, 2015 at 8:52 AM, Huang Ying <ying.huang@intel.com> wrote:
> > On Wed, 2015-01-07 at 08:24 -0700, Jens Axboe wrote:
> >> 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.
> >
> > I understand that null block is just for testing.
> >
> > I just think the message like:
> >
> > [ 1.971628] nullb0: unknown partition table
> >
> > may confuse the end user. They may think there are something wrong.
> > But it is not. Is there any way to suppress this?
>
> It can be logged for any normal block devices which have not be
> partitioned, and users should have understood that, IMO.
Then it is OK. Thanks for explanation.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-01-08 2:05 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
2015-01-07 15:24 ` [LKP] " 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 [this message]
2015-01-08 2:05 ` 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=1420682701.6201.79.camel@intel.com \
--to=ying.huang@intel.com \
--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.