All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas D." <whissi@whissi.de>
To: Jens Axboe <axboe@kernel.dk>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Date: Thu, 1 Oct 2015 13:58:55 +0200	[thread overview]
Message-ID: <560D1FFF.1090700@whissi.de> (raw)
In-Reply-To: <20151001101604.GA24150@kernel.dk>

Hi,

Jens Axboe wrote:
> Looking at the specific virtio_blk case, it does seem that it is
> checking the segment count before mapping. Does the below fix the
> problem, or does the BUG_ON() still trigger?

Have I understood you correctly, that I should test your patch against
linux-4.1.8?



PS: I upgraded several other systems (they are using dm with LUKS too
but are all ext4, no XFS like this VM) to linux-4.1.9, too and they all
freezed while running (booting was never a problem like with the system
using XFS). Some of them were running for hours until they freezed, some
freezed just seconds after start up finished.

Because I haven't seen the BUG_ON on any of these systems before with
linux-4.1.8 I am not sure if this is the same problem (and the system
with XFS from where I showed you the trace seems to boot fine with
linux-4.1.9 but now freezes, too). Any idea how to debug the freeze?


PS2: On Google I found
http://oss.sgi.com/pipermail/xfs/2014-November/039105.html -- that's why
I am mentioning that I am using XFS (and except to the file system the
VM is identical with the other VMs which didn't show any problems until
linux-4.1.9). I cannot find the patch from
http://oss.sgi.com/pipermail/xfs/2014-November/039149.html in the kernel
mainline. Is it worth to check that direction, too or doesn't the trace
indicate any relationship?


Thanks!


-Thomas

  reply	other threads:[~2015-10-01 11:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  1:10 kernel BUG at drivers/block/virtio_blk.c:172! Thomas D.
2015-10-01  9:00 ` req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!) Michael S. Tsirkin
2015-10-01  9:20   ` Hannes Reinecke
2015-10-01 13:09     ` Mike Snitzer
2015-10-01 13:36       ` Thomas D.
2015-10-01 13:36       ` Thomas D.
2015-10-01 15:35         ` Thomas D.
2015-10-01 16:06           ` Thomas D.
2015-10-01 16:06           ` Thomas D.
2015-10-01 15:35         ` Thomas D.
2015-10-01 13:09     ` Mike Snitzer
2015-10-01 10:16   ` Jens Axboe
2015-10-01 11:58     ` Thomas D. [this message]
2015-10-01 13:19     ` Michael S. Tsirkin
2015-10-01 11:55   ` Thomas D.

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=560D1FFF.1090700@whissi.de \
    --to=whissi@whissi.de \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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.