From: "Thomas D." <whissi@whissi.de>
To: Mike Snitzer <snitzer@redhat.com>, Hannes Reinecke <hare@suse.de>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.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 15:36:28 +0200 [thread overview]
Message-ID: <560D36DC.5050205@whissi.de> (raw)
In-Reply-To: <CAMM=eLcyT2JeWn4NJ6gjsHcRz_D8YcixLix64Spg9cVYFexGyA@mail.gmail.com>
Hi,
Mike Snitzer wrote:
> This particular dm-crypt on virtio-blk issue is fixed with this commit:
> http://git.kernel.org/linus/586b286b110e94eb31840ac5afc0c24e0881fe34
>
> Linus pulled this into v4.3-rc3.
I have this patch applied to linux-4.1.9. This could be the reason why I
don't see the issue on boot with linux-4.1.9.
So is the freeze I am experiencing with linux-4.1.9 another issue
introduced with linux-4.1.9 or another symptom/regression? Any idea?
-Thomas
next prev parent reply other threads:[~2015-10-01 13:43 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. [this message]
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.
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=560D36DC.5050205@whissi.de \
--to=whissi@whissi.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=mst@redhat.com \
--cc=snitzer@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.