leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

blk-mq: fix a typo and a spelling mistake

Browse Source 
Signed-off-by: Jens Axboe <axboe@fb.com>
This commit is contained in:
Jens Axboe 2017-03-29 11:10:34 -06:00
parent 018c259bbf
commit 48b99c9d65
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
block/blk-mq.c
View File

@ -525,7 +525,7 @@ EXPORT_SYMBOL(blk_mq_start_request);
/* /*
* When we reach here because queue is busy, REQ_ATOM_COMPLETE * When we reach here because queue is busy, REQ_ATOM_COMPLETE
* flag isn't set yet, so there may be race with timeout hanlder, * flag isn't set yet, so there may be race with timeout handler,
* but given rq->deadline is just set in .queue_rq() under * but given rq->deadline is just set in .queue_rq() under
* this situation, the race won't be possible in reality because * this situation, the race won't be possible in reality because
* rq->timeout should be set as big enough to cover the window * rq->timeout should be set as big enough to cover the window
@ -672,7 +672,7 @@ void blk_mq_rq_timed_out(struct request *req, bool reserved)
* just be ignored. This can happen due to the bitflag ordering. * just be ignored. This can happen due to the bitflag ordering.
* Timeout first checks if STARTED is set, and if it is, assumes * Timeout first checks if STARTED is set, and if it is, assumes
* the request is active. But if we race with completion, then * the request is active. But if we race with completion, then
* we both flags will get cleared. So check here again, and ignore * both flags will get cleared. So check here again, and ignore
* a timeout event with a request that isn't active. * a timeout event with a request that isn't active.
*/ */
if (!test_bit(REQ_ATOM_STARTED, &req->atomic_flags)) if (!test_bit(REQ_ATOM_STARTED, &req->atomic_flags))