From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 22 May 2018 23:02:08 +0200 From: Christoph Hellwig To: Jens Axboe Cc: Keith Busch , Bart Van Assche , linux-block@vger.kernel.org, Christoph Hellwig , Tejun Heo , Jianchao Wang , Ming Lei , Sebastian Ott , Sagi Grimberg , Israel Rukshin , Max Gurtovoy Subject: Re: [PATCH v13] blk-mq: Rework blk-mq timeout handling again Message-ID: <20180522210208.GA25444@lst.de> References: <20180522162515.20650-1-bart.vanassche@wdc.com> <448d63e9-cfcd-0bc8-abf3-30296590f1d6@kernel.dk> <20180522202657.GA8961@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-ID: On Tue, May 22, 2018 at 02:29:21PM -0600, Jens Axboe wrote: > > of BLK_EH_HANDLED. Is the driver supposed to return BLK_EH_NOT_HANDLED > > when the driver actually knows the request has been completed before > > returning the status? > > If the driver knows it's completed, it'd have to return BLK_EH_NOT_HANDLED. > Or BLK_EH_HANDLED would work too, since the above state transition would > then fail. Btw, I think we should just kill off BLK_EH_HANDLED. WIP totally untested progress toward that is here: http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/blk-eh-ret The only real missing bit is SCSI overloading the value for internal use.