[lkml]   [2017]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)
On 11/21/2017 10:27 AM, Jens Axboe wrote:
> On 11/21/2017 03:14 AM, Christian Borntraeger wrote:
>> Bisect points to
>> 1b5a7455d345b223d3a4658a9e5fce985b7998c1 is the first bad commit
>> commit 1b5a7455d345b223d3a4658a9e5fce985b7998c1
>> Author: Christoph Hellwig <>
>> Date: Mon Jun 26 12:20:57 2017 +0200
>> blk-mq: Create hctx for each present CPU
>> commit 4b855ad37194f7bdbb200ce7a1c7051fecb56a08 upstream.
>> Currently we only create hctx for online CPUs, which can lead to a lot
>> of churn due to frequent soft offline / online operations. Instead
>> allocate one for each present CPU to avoid this and dramatically simplify
>> the code.
>> Signed-off-by: Christoph Hellwig <>
>> Reviewed-by: Jens Axboe <>
>> Cc: Keith Busch <>
>> Cc:
>> Cc:
>> Link:
>> Signed-off-by: Thomas Gleixner <>
>> Cc: Oleksandr Natalenko <>
>> Cc: Mike Galbraith <>
>> Signed-off-by: Greg Kroah-Hartman <>
> I wonder if we're simply not getting the masks updated correctly. I'll
> take a look.

Can't make it trigger here. We do init for each present CPU, which means
that if I offline a few CPUs here and register a queue, those still show
up as present (just offline) and get mapped accordingly.

From the looks of it, your setup is different. If the CPU doesn't show
up as present and it gets hotplugged, then I can see how this condition
would trigger. What environment are you running this in? We might have
to re-introduce the cpu hotplug notifier, right now we just monitor
for a dead cpu and handle that.

Jens Axboe

 \ /
  Last update: 2017-11-21 19:10    [W:0.087 / U:9.704 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site