From: Jens Axboe <axboe@fb.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [block] 3d63546519: kernel BUG at block/bio.c:163!
Date: Wed, 2 Mar 2016 20:14:33 -0700 [thread overview]
Message-ID: <56D7AC19.5000307@fb.com> (raw)
In-Reply-To: <87d1rcpda3.fsf@yhuang-dev.intel.com>
On 03/02/2016 06:21 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git io-streamid
> commit 3d63546519428f2ed1b79e93e4321cf37c5a0d83 ("block: add support for carrying a stream ID in a bio")
>
>
> udevd[279]: failed to execute '/sbin/modprobe' '/sbin/modprobe -bv of:Ni2c-test-busT<NULL>Cunittest-i2c-bus': No such file or directory
> [ 3.768664] ------------[ cut here ]------------
> [ 3.768664] ------------[ cut here ]------------
> [ 3.769406] kernel BUG at block/bio.c:163!
> [ 3.769406] kernel BUG at block/bio.c:163!
It's a known bug, it's fixed in the current branch.
--
Jens Axboe
prev parent reply other threads:[~2016-03-03 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 1:21 [lkp] [block] 3d63546519: kernel BUG at block/bio.c:163! kernel test robot
2016-03-03 3:14 ` Jens Axboe [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=56D7AC19.5000307@fb.com \
--to=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@linux.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