From: Jens Axboe <axboe@kernel.dk>
To: Rusty Russell <rusty@rustcorp.com.au>,
Jeff Layton <jlayton@poochiereds.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
Dave Chinner <david@fromorbit.com>
Cc: Ming Lei <tom.leiming@gmail.com>,
xfs@oss.sgi.com, virtualization@lists.linux-foundation.org
Subject: Re: kernel BUG at drivers/block/virtio_blk.c:172!
Date: Mon, 10 Nov 2014 16:31:51 -0700 [thread overview]
Message-ID: <54614AE7.2080204@kernel.dk> (raw)
In-Reply-To: <87bnofnzop.fsf@rustcorp.com.au>
On 2014-11-10 02:59, Rusty Russell wrote:
> Jeff Layton <jlayton@poochiereds.net> writes:
>
>> In the latest Fedora rawhide kernel in the repos, I'm seeing the
>> following oops when mounting xfs. rc2-ish kernels seem to be fine:
>>
>> [ 64.669633] ------------[ cut here ]------------
>> [ 64.670008] kernel BUG at drivers/block/virtio_blk.c:172!
>
> Hmm, that's:
>
> BUG_ON(req->nr_phys_segments + 2 > vblk->sg_elems);
>
> But during our probe routine we said:
>
> /* We can handle whatever the host told us to handle. */
> blk_queue_max_segments(q, vblk->sg_elems-2);
>
> Jens?
Known, I'm afraid, Ming is looking into it.
--
Jens Axboe
next prev parent reply other threads:[~2014-11-10 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141107080416.0837a88c@tlielax.poochiereds.net>
2014-11-10 9:59 ` kernel BUG at drivers/block/virtio_blk.c:172! Rusty Russell
2014-11-10 23:31 ` Jens Axboe [this message]
2014-11-11 0:56 ` Ming Lei
[not found] ` <CACVXFVOgRMqCUASOaXQ7ys8yiKZFEH5SA-+mV=H0uvHuGseENQ@mail.gmail.com>
2014-11-11 15:42 ` Dongsu Park
2014-11-11 16:42 ` Ming Lei
[not found] ` <CACVXFVNXSmw=Gu_9JAtpF3uxupSMr4kN2ge-jnZMxZAMcaHrfw@mail.gmail.com>
2014-11-12 18:18 ` Jens Axboe
2014-11-12 21:02 ` Jeff Layton
2014-11-13 11:04 ` Dongsu Park
2015-10-01 1:10 Thomas D.
-- strict thread matches above, loose matches on Subject: below --
2014-11-07 13:04 Jeff Layton
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=54614AE7.2080204@kernel.dk \
--to=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=jlayton@poochiereds.net \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tom.leiming@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xfs@oss.sgi.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).