From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)
Date: Wed, 22 Nov 2017 08:28:57 +0100 [thread overview]
Message-ID: <20171122072857.GA19338@lst.de> (raw)
In-Reply-To: <08e6f35a-4f49-973e-99f7-6087b44337c4@kernel.dk>
Jens, please don't just revert the commit in your for-linus tree.
On its own this will totally mess up the interrupt assignments. Give
me a bit of time to sort this out properly.
next prev parent reply other threads:[~2017-11-22 7:28 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 14:42 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk Christian Borntraeger
2017-11-20 19:20 ` Bart Van Assche
2017-11-20 19:29 ` Christian Borntraeger
2017-11-20 19:29 ` Christian Borntraeger
2017-11-20 19:42 ` Jens Axboe
2017-11-20 20:49 ` Christian Borntraeger
2017-11-20 20:52 ` Jens Axboe
2017-11-21 8:35 ` Christian Borntraeger
2017-11-21 9:50 ` Christian Borntraeger
2017-11-21 10:14 ` 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable) Christian Borntraeger
2017-11-21 10:14 ` Christian Borntraeger
2017-11-21 17:27 ` Jens Axboe
2017-11-21 18:09 ` Jens Axboe
2017-11-21 18:09 ` Jens Axboe
2017-11-21 18:12 ` Christian Borntraeger
2017-11-21 18:27 ` Jens Axboe
2017-11-21 18:39 ` Jens Axboe
2017-11-21 19:15 ` Christian Borntraeger
2017-11-21 19:15 ` Christian Borntraeger
2017-11-21 19:30 ` Jens Axboe
2017-11-21 20:12 ` Christian Borntraeger
2017-11-21 20:12 ` Christian Borntraeger
2017-11-21 20:14 ` Jens Axboe
2017-11-21 20:19 ` Christian Borntraeger
2017-11-21 20:21 ` Jens Axboe
2017-11-21 20:21 ` Jens Axboe
2017-11-21 20:31 ` Christian Borntraeger
2017-11-21 20:39 ` Jens Axboe
2017-11-22 7:28 ` Christoph Hellwig
2017-11-22 7:28 ` Christoph Hellwig [this message]
2017-11-22 14:46 ` Jens Axboe
2017-11-23 14:34 ` Christoph Hellwig
2017-11-23 14:42 ` Hannes Reinecke
2017-11-23 14:47 ` Christoph Hellwig
2017-11-23 15:05 ` Christian Borntraeger
2017-11-23 18:17 ` Christian Borntraeger
2017-11-23 18:25 ` Christoph Hellwig
2017-11-23 18:28 ` Christian Borntraeger
2017-11-23 18:32 ` Christoph Hellwig
2017-11-23 18:59 ` Christian Borntraeger
2017-11-24 13:09 ` Christian Borntraeger
2017-11-27 15:54 ` Christoph Hellwig
2017-11-29 19:18 ` Christian Borntraeger
2017-11-29 19:36 ` Christian Borntraeger
2017-12-04 16:21 ` Christoph Hellwig
2017-12-06 12:25 ` Christian Borntraeger
2017-12-06 12:25 ` Christian Borntraeger
2017-12-06 23:29 ` Christoph Hellwig
2017-12-07 9:20 ` Christian Borntraeger
2017-12-14 17:32 ` Christian Borntraeger
2017-12-18 13:56 ` Stefan Haberland
2017-12-20 15:47 ` Christian Borntraeger
2018-01-11 9:13 ` Ming Lei
2018-01-11 9:13 ` Ming Lei
2018-01-11 9:26 ` Stefan Haberland
2018-01-11 11:44 ` Christian Borntraeger
2018-01-11 13:17 ` Stefan Haberland
2018-01-11 17:46 ` Christoph Hellwig
2018-01-12 1:16 ` Ming Lei
2017-11-22 14:46 ` Jens Axboe
2017-11-21 20:39 ` Jens Axboe
2017-11-21 20:31 ` Christian Borntraeger
2017-11-21 20:19 ` Christian Borntraeger
2017-11-21 19:30 ` Jens Axboe
2017-11-23 14:02 ` Christoph Hellwig
2017-11-23 14:02 ` Christoph Hellwig
2017-11-23 14:08 ` Christoph Hellwig
2017-11-23 14:08 ` Christoph Hellwig
2017-11-21 18:12 ` Christian Borntraeger
2017-11-21 17:27 ` Jens Axboe
2017-11-21 9:50 ` 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk Christian Borntraeger
2017-11-20 20:49 ` Christian Borntraeger
2017-11-20 19:42 ` Jens Axboe
2017-11-20 19:20 ` Bart Van Assche
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=20171122072857.GA19338@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stable@vger.kernel.org \
--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.