Skip to content

Commit

Permalink
block: warn if tag is greater than real_max_depth.
Browse files Browse the repository at this point in the history
In case tag depth is reduced, it is max_depth not real_max_depth.
So we should allow a request with tag >= max_depth, but for a
tag >= real_max_depth, there really should be some problem.

Signed-off-by: Tao Ma <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
  • Loading branch information
taoma-tm authored and axboe committed Oct 25, 2011
1 parent 8315722 commit 5e08159
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions block/blk-tag.c
Original file line number Diff line number Diff line change
Expand Up @@ -286,12 +286,14 @@ void blk_queue_end_tag(struct request_queue *q, struct request *rq)

BUG_ON(tag == -1);

if (unlikely(tag >= bqt->real_max_depth))
if (unlikely(tag >= bqt->max_depth)) {
/*
* This can happen after tag depth has been reduced.
* FIXME: how about a warning or info message here?
* But tag shouldn't be larger than real_max_depth.
*/
WARN_ON(tag >= bqt->real_max_depth);
return;
}

list_del_init(&rq->queuelist);
rq->cmd_flags &= ~REQ_QUEUED;
Expand Down

0 comments on commit 5e08159

Please sign in to comment.