From: Eric Sesterhenn / Snakebyte <snakebyte@gmx.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henk Vergonet <Henk.Vergonet@gmail.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Eric Sesterhenn <snakebyte@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [Patch] Off by one in drivers/usb/input/yealink.c
Date: Thu, 6 Jul 2006 02:49:11 +0200 [thread overview]
Message-ID: <20060706004911.GA3563@alice> (raw)
In-Reply-To: <d120d5000607050655o44cb66c3s7616493c7507d4d8@mail.gmail.com>
* Dmitry Torokhov (dmitry.torokhov@gmail.com) wrote:
> On 7/5/06, Henk Vergonet <Henk.Vergonet@gmail.com> wrote:
> >On Tue, Jun 27, 2006 at 03:51:43PM -0700, Randy.Dunlap wrote:
> >> On Wed, 28 Jun 2006 00:41:19 +0200 Eric Sesterhenn wrote:
> >> > another off by one spotted by coverity (id #485),
> >> > we loop exactly one time too often
> >> >
> >> > Signed-off-by: Eric Sesterhenn <snakebyte@gmx.de>
> >> >
> >> > --- linux-2.6.17-git11/drivers/usb/input/yealink.c.orig 2006-06-28
> >00:29:46.000000000 +0200
> >> > +++ linux-2.6.17-git11/drivers/usb/input/yealink.c 2006-06-28
> >00:30:04.000000000 +0200
> >> > @@ -350,7 +350,7 @@ static int yealink_do_idle_tasks(struct
> >> > val = yld->master.b[ix];
> >> > if (val != yld->copy.b[ix])
> >> > goto send_update;
> >> > - } while (++ix < sizeof(yld->master));
> >> > + } while (++ix < sizeof(yld->master)-1);
> >
> >Apart from introducing a new bug in the code, the construct is ugly.
> >
> >I would rather see then the more readable:
> >
> > ix++;
> > } while (ix < sizeof(yld->master));
> >
>
> The new code is exactly the same as the old one; however I do not see
> the problem with the old code. Could it be that Coverity got confused
> by prefix vs. postfix increment?
I looked at this code several times too, and tried to reproduce the bug
with the following little program:
#include <string.h>
int main(int argc, char **argv) {
char foo[] = "abcdef";
int i = 0;
foo[strlen(foo)] = 'X';
do {
putchar(foo[i]);
} while (++i < sizeof(foo));
}
Which clearly shows that the terminating '\0' gets printed too,
replaced by the X for better visibility, so the code
runs past the array, or did I fail to replicate the original
code somewhere?
Eric
next prev parent reply other threads:[~2006-07-06 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 22:41 [Patch] Off by one in drivers/usb/input/yealink.c Eric Sesterhenn
2006-06-27 22:51 ` Randy.Dunlap
2006-06-27 23:04 ` Eric Sesterhenn / Snakebyte
2006-06-27 23:18 ` Randy.Dunlap
2006-06-27 23:26 ` Eric Sesterhenn
2006-07-05 13:02 ` Henk Vergonet
[not found] ` <d120d5000607050655o44cb66c3s7616493c7507d4d8@mail.gmail.com>
2006-07-06 0:49 ` Eric Sesterhenn / Snakebyte [this message]
2006-07-06 2:25 ` Dmitry Torokhov
2006-07-06 14:41 ` Eric Sesterhenn / Snakebyte
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=20060706004911.GA3563@alice \
--to=snakebyte@gmx.de \
--cc=Henk.Vergonet@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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