Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
48b99c9d
Commit
48b99c9d
authored
Mar 29, 2017
by
Jens Axboe
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
blk-mq: fix a typo and a spelling mistake
Signed-off-by:
Jens Axboe
<
axboe@fb.com
>
parent
018c259b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
block/blk-mq.c
block/blk-mq.c
+2
-2
No files found.
block/blk-mq.c
View file @
48b99c9d
...
@@ -525,7 +525,7 @@ EXPORT_SYMBOL(blk_mq_start_request);
...
@@ -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 han
ld
er,
* flag isn't set yet, so there may be race with timeout han
dl
er,
* 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)
...
@@ -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
))
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment