[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111221132029.GK20129@parisc-linux.org>
Date: Wed, 21 Dec 2011 06:20:29 -0700
From: Matthew Wilcox <matthew@....cx>
To: "Williams, Dan J" <dan.j.williams@...el.com>
Cc: Tao Ma <tm@....ma>, Meelis Roos <mroos@...ux.ee>, axboe@...nel.dk,
Tao Ma <boyu.mt@...bao.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, Ed Nadolski <edmund.nadolski@...el.com>
Subject: Re: [PATCH] block: fix blk_queue_end_tag()
On Tue, Dec 20, 2011 at 11:30:14PM -0800, Williams, Dan J wrote:
> @@ -284,16 +284,7 @@ void blk_queue_end_tag(struct request_queue *q,
> struct request *rq)
> struct blk_queue_tag *bqt = q->queue_tags;
> int tag = rq->tag;
>
> - BUG_ON(tag == -1);
> -
> - if (unlikely(tag >= bqt->max_depth)) {
> - /*
> - * This can happen after tag depth has been reduced.
> - * But tag shouldn't be larger than real_max_depth.
> - */
> - WARN_ON(tag >= bqt->real_max_depth);
> - return;
> - }
> + BUG_ON(tag == -1 || tag > bqt->real_max_depth);
or ...
- int tag = rq->tag;
+ unsigned tag = rq->tag;
+ BUG_ON(tag >= bqt->real_max_depth);
since tags in the range INT_MIN to -2 are also a bug, right?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists