Thread (2 messages) 2 messages, 2 authors, 2016-08-29

Re: Oops when completing request on the wrong queue

From: Gabriel Krisman Bertazi <hidden>
Date: 2016-08-29 18:06:21
Also in: linux-nvme, linux-scsi

Jens Axboe [off-list ref] writes:
quoted
Can you try this patch? It's not perfect, but I'll be interested if it
makes a difference for you.
Hi Jens,

Sorry for the delay.  I just got back to this and have been running your
patch on top of 4.8 without a crash for over 1 hour.  I wanna give it
more time to make sure it's running properly, though.

Let me get back to you after a few more rounds of test.
This one should handle the WARN_ON() for running the hw queue on the
wrong CPU as well.
On the workaround you added to prevent WARN_ON, we surely need to
prevent blk_mq_hctx_next_cpu from scheduling dead cpus in the first
place, right..  How do you feel about the following RFC?  I know it's
not a complete fix, but it feels like a good improvement to me.

http://www.spinics.net/lists/linux-scsi/msg98608.html

-- 
Gabriel Krisman Bertazi
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help