[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171229100747.GC4020@infradead.org>
Date: Fri, 29 Dec 2017 02:07:47 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Tejun Heo <tj@...nel.org>
Cc: jack@...e.cz, axboe@...nel.dk, clm@...com, jbacik@...com,
kernel-team@...com, linux-kernel@...r.kernel.org,
linux-btrfs@...r.kernel.org, peterz@...radead.org,
jianchao.w.wang@...cle.com, Bart.VanAssche@....com,
Asai Thambi SP <asamymuthupa@...ron.com>,
Stefan Haberland <sth@...ux.vnet.ibm.com>,
Jan Hoeppner <hoeppner@...ux.vnet.ibm.com>
Subject: Re: [PATCH 4/7] blk-mq: make blk_abort_request() trigger timeout path
On Sat, Dec 16, 2017 at 04:07:23AM -0800, Tejun Heo wrote:
> Note that this makes blk_abort_request() asynchronous - it initiates
> abortion but the actual termination will happen after a short while,
> even when the caller owns the request. AFAICS, SCSI and ATA should be
> fine with that and I think mtip32xx and dasd should be safe but not
> completely sure. It'd be great if people who know the drivers take a
> look.
For that you'll need to CC linux-ide and linux-scsi, and for the
SAS drivers some of the usual suspects that touch the SAS code.
Powered by blists - more mailing lists