From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751919AbeDJUqL (ORCPT ); Tue, 10 Apr 2018 16:46:11 -0400 Received: from mondschein.lichtvoll.de ([194.150.191.11]:37753 "EHLO mail.lichtvoll.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751546AbeDJUqK (ORCPT ); Tue, 10 Apr 2018 16:46:10 -0400 Authentication-Results: auth=pass smtp.auth=martin smtp.mailfrom=martin@lichtvoll.de From: Martin Steigerwald To: Martin Steigerwald Cc: Tejun Heo , Sitsofe Wheeler , Jens Axboe , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Stefan Haberland , Jan Hoeppner , Bart Van Assche Subject: Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request Date: Tue, 10 Apr 2018 22:46:07 +0200 Message-ID: <2410059.9M3ptFeZvf@merkaba> In-Reply-To: <2699418.6CV4rbzP8d@merkaba> References: <20180402220458.GJ388343@devbig577.frc2.facebook.com> <2699418.6CV4rbzP8d@merkaba> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Martin Steigerwald - 10.04.18, 20:43: > Tejun Heo - 03.04.18, 00:04: > > Request abortion is performed by overriding deadline to now and > > scheduling timeout handling immediately. For the latter part, the > > code was using mod_timer(timeout, 0) which can't guarantee that the > > timer runs afterwards. Let's schedule the underlying work item > > directly instead. > > > > This fixes the hangs during probing reported by Sitsofe but it isn't > > yet clear to me how the failure can happen reliably if it's just the > > above described race condition. > > Compiling a 4.16.1 kernel with that patch to test whether this fixes > the boot hang I reported in: > > [Possible REGRESSION, 4.16-rc4] Error updating SMART data during > runtime and boot failures with blk_mq_terminate_expired in backtrace > https://bugzilla.kernel.org/show_bug.cgi?id=199077 Fails as well, see https://bugzilla.kernel.org/show_bug.cgi?id=199077#c8 for photo with (part of) backtrace. > The "Error updating SMART data during runtime" thing I reported there > as well may still be another (independent) issue. > > > Signed-off-by: Tejun Heo > > Reported-by: Sitsofe Wheeler > > Reported-by: Meelis Roos > > Fixes: 358f70da49d7 ("blk-mq: make blk_abort_request() trigger > > timeout path") Cc: stable@vger.kernel.org # v4.16 > > Link: > > http://lkml.kernel.org/r/CALjAwxh-PVYFnYFCJpGOja+m5SzZ8Sa4J7ohxdK=r8 > > NyOF-EM A@mail.gmail.com Link: > > http://lkml.kernel.org/r/alpine.LRH.2.21.1802261049140.4893@math.ut. > > ee --- Hello, > > > > I don't have the full explanation yet but here's a preliminary > > patch. > > > > Thanks. > > > > block/blk-timeout.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/block/blk-timeout.c b/block/blk-timeout.c > > index a05e367..f0e6e41 100644 > > --- a/block/blk-timeout.c > > +++ b/block/blk-timeout.c > > @@ -165,7 +165,7 @@ void blk_abort_request(struct request *req) > > > > * No need for fancy synchronizations. > > */ > > > > blk_rq_set_deadline(req, jiffies); > > > > - mod_timer(&req->q->timeout, 0); > > + kblockd_schedule_work(&req->q->timeout_work); > > > > } else { > > > > if (blk_mark_rq_complete(req)) > > > > return; -- Martin