From: Jens Axboe <jaxboe@fusionio.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] cciss: call BUG() earlier
Date: Tue, 01 Jun 2010 10:17:20 +0000 [thread overview]
Message-ID: <20100601101720.GK3564@kernel.dk> (raw)
In-Reply-To: <20100601070544.GC5483@bicker>
On Tue, Jun 01 2010, Darren Jenkins wrote:
> Hi Dan,
>
> On Tue, Jun 1, 2010 at 5:05 PM, Dan Carpenter <error27@gmail.com> wrote:
> > I moved the range check after the increment. The current code would
> > write past the end of the array once before calling BUG().
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> >
> > diff --git a/drivers/block/cciss_scsi.c b/drivers/block/cciss_scsi.c
> > index e1d0e2c..3381505 100644
> > --- a/drivers/block/cciss_scsi.c
> > +++ b/drivers/block/cciss_scsi.c
> > @@ -188,11 +188,11 @@ scsi_cmd_free(ctlr_info_t *h, CommandList_struct *cmd)
> >
> > sa = h->scsi_ctlr;
> > stk = &sa->cmd_stack;
> > + stk->top++;
> > if (stk->top >= CMD_STACK_SIZE) {
> > printk("cciss: scsi_cmd_free called too many times.\n");
> > BUG();
> > }
> > - stk->top++;
> > stk->elem[stk->top] = (struct cciss_scsi_cmd_stack_elem_t *) cmd;
> > }
>
> Did you diff this one backwards ?
>
How so? if stk->top = CMD_STACK_SIZE - 1 the current code will not
trigger the BUG, but it will index beyond the size of ->elem. So the
patch looks correct to me.
Dan, I'll apply it, thanks.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-01 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 7:05 [patch] cciss: call BUG() earlier Dan Carpenter
2010-06-01 9:44 ` Darren Jenkins
2010-06-01 10:17 ` Jens Axboe [this message]
2010-06-01 10:26 ` Darren Jenkins
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=20100601101720.GK3564@kernel.dk \
--to=jaxboe@fusionio.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.