From: Christoph Hellwig <hch@lst.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)
Date: Mon, 27 Nov 2017 16:54:09 +0100 [thread overview]
Message-ID: <20171127155409.GA6937@lst.de> (raw)
In-Reply-To: <419d8565-9cbe-16ac-3d5d-5945098694bc@de.ibm.com>
Can you try this git branch:
git://git.infradead.org/users/hch/block.git blk-mq-hotplug-fix
Gitweb:
http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/blk-mq-hotplug-fix
next prev parent reply other threads:[~2017-11-27 15:54 UTC|newest]
Thread overview: 52+ 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: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 17:27 ` 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:30 ` Jens Axboe
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:31 ` Christian Borntraeger
2017-11-21 20:39 ` Jens Axboe
2017-11-22 7:28 ` Christoph Hellwig
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 [this message]
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 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: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-23 14:02 ` Christoph Hellwig
2017-11-23 14:08 ` Christoph Hellwig
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=20171127155409.GA6937@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).