From: Jens Axboe <axboe@kernel.dk>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: Tao Ma <tm@tao.ma>, Meelis Roos <mroos@linux.ee>,
Tao Ma <boyu.mt@taobao.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org,
Ed Nadolski <edmund.nadolski@intel.com>
Subject: Re: [PATCH] block: fix blk_queue_end_tag()
Date: Wed, 21 Dec 2011 11:05:11 +0100 [thread overview]
Message-ID: <4EF1AF57.2010307@kernel.dk> (raw)
In-Reply-To: <CABE8wwsRDjNs=UjBG071=AF7-h7RB+NNrQzPMREypNwSpYAVPA@mail.gmail.com>
On 2011-12-21 09:22, Williams, Dan J wrote:
> On Wed, Dec 21, 2011 at 12:16 AM, Tao Ma <tm@tao.ma> wrote:
>> On 12/21/2011 03:30 PM, Williams, Dan J wrote:
>>> On Tue, Dec 20, 2011 at 10:48 PM, Tao Ma <tm@tao.ma> wrote:
>>>> On 12/21/2011 02:36 PM, Meelis Roos wrote:
>>>>>>> - if (unlikely(tag >= bqt->max_depth)) {
>>>>>>> + if (WARN_ONCE(tag >= bqt->real_max_depth,
>>>>>>> + "%s: tag %d greater than tag map size: %d\n",
>>>>>>> + __func__, tag, bqt->real_max_depth)) {
>>>>>>> /*
>>>>>>> * This can happen after tag depth has been reduced.
>>>>>> Please also change the comments here since it should never happen in the
>>>>>> right workload.
>>>>>
>>>>> What do you mean by right workload? Normal workload?
>>>> yeah, so real_max_depth is the maximum depth we ever have. So in normal
>>>> case(shrinking queue depth is also a normal user case), we should never
>>>> arrive here. In another word, if tag >= real_max_depth, we should have a
>>>> bug in the kernel.
>>>
>>> So this is what Ed Nadolski suggested, just cut to the chase and do,
>>> the following. Seems like the comment is what got us into trouble in
>>> the first place.
>>>
>>> diff --git a/block/blk-tag.c b/block/blk-tag.c
>>> index e74d6d1..e297d9d7 100644
>>> --- a/block/blk-tag.c
>>> +++ b/block/blk-tag.c
>>> @@ -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);
>> I guess tag = bqt->real_max_depth should also be a problem.
>
> Yes, sorry, should have been >=
Can you resend a v2 and I'll get it applied, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2011-12-21 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 23:33 [PATCH] block: fix blk_queue_end_tag() Dan Williams
2011-12-21 6:33 ` Tao Ma
2011-12-21 6:36 ` Meelis Roos
2011-12-21 6:48 ` Tao Ma
2011-12-21 7:30 ` Williams, Dan J
2011-12-21 8:16 ` Tao Ma
2011-12-21 8:22 ` Williams, Dan J
2011-12-21 10:05 ` Jens Axboe [this message]
2011-12-21 13:20 ` Matthew Wilcox
2011-12-21 17:37 ` Williams, Dan J
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF1AF57.2010307@kernel.dk \
--to=axboe@kernel.dk \
--cc=boyu.mt@taobao.com \
--cc=dan.j.williams@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=tm@tao.ma \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).