[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a83ju6av.fsf@concordia.ellerman.id.au>
Date: Tue, 01 Aug 2017 16:54:16 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Brian King <brking@...ux.vnet.ibm.com>
Cc: Jens Axboe <axboe@...nel.dk>, Brian J King <bjking1@...ibm.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block\@vger.kernel.org" <linux-block@...r.kernel.org>,
Bart Van Assche <Bart.VanAssche@....com>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: blk_mq_sched_insert_request: inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage
Michael Ellerman <mpe@...erman.id.au> writes:
> Brian King <brking@...ux.vnet.ibm.com> writes:
>
>> On 07/28/2017 10:17 AM, Brian J King wrote:
>>> Jens Axboe <axboe@...nel.dk> wrote on 07/28/2017 09:25:48 AM:
>>>
>>>> Can you try the below fix? Should be more palatable than the previous
>>>> one. Brian, maybe you can take a look at the IRQ issue mentioned above?
>>
>> Michael,
>>
>> Does this address the issue you are seeing?
>
> Yes it seems to, thanks.
>
> I only see the trace on reboot, and not 100% of the time. But I've
> survived a couple of reboots now without seeing anything, so I think
> this is helping.
>
> I'll put the patch in my Jenkins over night and let you know how it
> survives that, which should be ~= 25 boots.
No lockdep warnings or other oddness over night, so that patch looks
good to me.
cheers
Powered by blists - more mailing lists