On Tue, Oct 29, 2019 at 09:22:26AM +0000, John Garry wrote: > On 29/10/2019 01:50, Ming Lei wrote: > > On Mon, Oct 28, 2019 at 11:55:42AM +0000, John Garry wrote: > > > > > > > > > > For the SCSI commands which timeout, I notice that > > > > > scsi_set_blocked(reason=SCSI_MLQUEUE_EH_RETRY) was called 30 seconds > > > > > earlier. > > > > > > > > > > scsi_set_blocked+0x20/0xb8 > > > > > __scsi_queue_insert+0x40/0x90 > > > > > scsi_softirq_done+0x164/0x1c8 > > > > > __blk_mq_complete_request_remote+0x18/0x20 > > > > > flush_smp_call_function_queue+0xa8/0x150 > > > > > generic_smp_call_function_single_interrupt+0x10/0x18 > > > > > handle_IPI+0xec/0x1a8 > > > > > arch_cpu_idle+0x10/0x18 > > > > > do_idle+0x1d0/0x2b0 > > > > > cpu_startup_entry+0x24/0x40 > > > > > secondary_start_kernel+0x1b4/0x208 > > > > > > > > Could you investigate a bit the reason why timeout is triggered? > > > > > > Yeah, it does seem a strange coincidence that the SCSI command even failed > > > and we have to retry, since these should be uncommon events. I'll check on > > > this LLDD error. > > > > > > > > > > > Especially we suppose to drain all in-flight requests before the > > > > last CPU of this hctx becomes offline, and it shouldn't be caused by > > > > the hctx becoming dead, so still need you to confirm that all > > > > in-flight requests are really drained in your test. > > > > > > ok > > > > > > Or is it still > > > > possible to dispatch to LDD after BLK_MQ_S_INTERNAL_STOPPED is set? > > > > > > It shouldn't be. However it would seem that this IO had been dispatched to > > > the LLDD, the hctx dies, and then we attempt to requeue on that hctx. > > > > But this patch does wait for completion of in-flight request before > > shutdown the last CPU of this hctx. > > > > Hi Ming, > > It may actually be a request from a hctx which is not shut down which errors > and causes the time out. I'm still checking. If that is the case, blk_mq_hctx_drain_inflight_rqs() will wait for completion of this request. The only chance it is missed is that the last CPU of this hctx becomes offline just when this request stays in request list after it is retried from EH. > > BTW, Can you let me know exactly where you want the debug for "Or > blk_mq_hctx_next_cpu() may still run WORK_CPU_UNBOUND schedule after > all CPUs are offline, could you add debug message in that branch?" You can add the following debug message, then reproduce the issue and see if the debug log is dumped. diff --git a/block/blk-mq.c b/block/blk-mq.c index 06081966549f..5a98a7b79c0d 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -1452,6 +1452,10 @@ static int blk_mq_hctx_next_cpu(struct blk_mq_hw_ctx *hctx) */ hctx->next_cpu = next_cpu; hctx->next_cpu_batch = 1; + + printk(KERN_WARNING "CPU %d, schedule from (dead) hctx %s\n", + raw_smp_processor_id(), + cpumask_empty(hctx->cpumask) ? "inactive": "active"); return WORK_CPU_UNBOUND; } Thanks, Ming
