diff options
author | Christoph Hellwig <hch@lst.de> | 2018-11-14 19:02:06 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-11-15 22:13:18 +0300 |
commit | 39795d6534c6e698c4f9c065e0a5f4a2e5af7543 (patch) | |
tree | 2abe3b44e067bd726bba39786a4072709b96364c /block/blk-timeout.c | |
parent | 079076b3416e78ba2bb3ce38e05e320c388c3120 (diff) | |
download | linux-39795d6534c6e698c4f9c065e0a5f4a2e5af7543.tar.xz |
block: don't hold the queue_lock over blk_abort_request
There is nothing it could synchronize against, so don't go through
the pains of acquiring the lock.
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-timeout.c')
-rw-r--r-- | block/blk-timeout.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/blk-timeout.c b/block/blk-timeout.c index 3b0179fbdd6a..124c26128bf6 100644 --- a/block/blk-timeout.c +++ b/block/blk-timeout.c @@ -75,7 +75,7 @@ ssize_t part_timeout_store(struct device *dev, struct device_attribute *attr, * This function requests that the block layer start recovery for the * request by deleting the timer and calling the q's timeout function. * LLDDs who implement their own error recovery MAY ignore the timeout - * event if they generated blk_abort_req. Must hold queue lock. + * event if they generated blk_abort_request. */ void blk_abort_request(struct request *req) { |