public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Constantin Baranov <const@const.mimas.ru>,
	linux-kernel@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [PATCH 2.6.27-rc3] led: driver for LEDs on PCEngines ALIX.2 and ALIX.3 boards
Date: Fri, 22 Aug 2008 21:44:28 +0200	[thread overview]
Message-ID: <20080822194428.GB31789@1wt.eu> (raw)
In-Reply-To: <20080822115150.6b3907a4.akpm@linux-foundation.org>

Hi Andrew,

On Fri, Aug 22, 2008 at 11:51:50AM -0700, Andrew Morton wrote:
> On Tue, 19 Aug 2008 22:23:41 +0500
> Constantin Baranov <const@const.mimas.ru> wrote:
> > +static int __init alix_led_probe(struct platform_device *pdev)
> > +{
> > +	int i;
> > +	int ret = 0;
> > +	
> > +	for (i = 0; i < ARRAY_SIZE(alix_leds) && ret >= 0; i++)
> > +		ret = led_classdev_register(&pdev->dev, &alix_leds[i].cdev);
> > +
> > +	if (ret < 0) {
> > +		for (i = i - 2; i >= 0; i--)
> 
> this is off-by-one, surely.
> 
> If we get here with i==1, we'll loop 4 billion times.

No we will not because i is signed. We'll simply not enter the loop.
However, the code looks suspicious and the reasoning behind i-2 isn't
quite clear.

Willy


  reply	other threads:[~2008-08-22 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 17:23 [PATCH 2.6.27-rc3] led: driver for LEDs on PCEngines ALIX.2 and ALIX.3 boards Constantin Baranov
2008-08-22 18:51 ` Andrew Morton
2008-08-22 19:44   ` Willy Tarreau [this message]
2008-08-22 21:08   ` Constantin Baranov
2008-08-22 21:31     ` Andrew Morton
2008-08-23 17:11       ` Constantin Baranov
2008-08-24  5:36         ` Andrew Morton
2008-08-24 10:08   ` Stefan Richter
2008-08-24 10:33     ` Stefan Richter

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=20080822194428.GB31789@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=const@const.mimas.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.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