virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas D." <whissi@whissi.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, 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:55:39 +0200	[thread overview]
Message-ID: <560D1F3B.3000400@whissi.de> (raw)
In-Reply-To: <20151001114817-mutt-send-email-mst@redhat.com>

Hi,

Michael S. Tsirkin wrote:
> To debug this,
> maybe you can print out sg_elems at init time and when this fails,
> to make sure some kind of memory corruption
> does not change sg_elems after initialization?

If that was addressed to me could you please tell me how to do that?


-Thomas

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

Thread overview: 11+ 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
     [not found]     ` <CAMM=eLcyT2JeWn4NJ6gjsHcRz_D8YcixLix64Spg9cVYFexGyA@mail.gmail.com>
2015-10-01 13:36       ` Thomas D.
     [not found]       ` <560D36DC.5050205@whissi.de>
2015-10-01 15:35         ` Thomas D.
     [not found]         ` <560D52DE.3020303@whissi.de>
2015-10-01 16:06           ` Thomas D.
2015-10-01 10:16   ` Jens Axboe
2015-10-01 11:58     ` Thomas D.
2015-10-01 13:19     ` Michael S. Tsirkin
2015-10-01 11:55   ` Thomas D. [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=560D1F3B.3000400@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 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).