linux-kernel - Re: [PATCH] leds: Add WM8350 LED driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081126181710.GH6234@sirena.org.uk>
Date:	Wed, 26 Nov 2008 18:17:11 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Sven Wegener <sven.wegener@...aler.net>
Cc:	Richard Purdie <rpurdie@...ys.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] leds: Add WM8350 LED driver

On Wed, Nov 26, 2008 at 06:39:04PM +0100, Sven Wegener wrote:

You should cut irrelevant text from your mail; it makes it much easier
to find what you're actually saying - if you've got hundreds of lines of
unbroken quoted text it's easy to page straight past small comments.

> On Wed, 26 Nov 2008, Mark Brown wrote:

> > +	isink = regulator_get(&pdev->dev, "led_isink");
> > +	if (IS_ERR(isink) || isink == NULL) {
> > +		printk(KERN_ERR "%s: cant get ISINK\n", __func__);
> > +		return PTR_ERR(isink);

> Uhm, if isink is ever NULL, which according to your check above you
> expect it to happen, this will return 0, meaning success. I'm not sure
> if this is what you want and looking at regulator_get() it should never
> be NULL.

No, it should never be NULL - this is was inherited from the out of tree
history.

> > +	for (i = 0; i < ARRAY_SIZE(isink_cur) - 1; i++)

> This loop will skip the last array member.

This is intentional, it ensures that we always end up pointing to a
value within the array.

> > +int wm8350_register_led(struct wm8350 *wm8350, int lednum, int dcdc, int isink,
> > +			struct wm8350_led_platform_data *pdata)
> > +{
> > +	struct wm8350_led *led = &wm8350->pmic.led[lednum];
> > +	struct platform_device *pdev;
> > +	int ret;
> > +
> > +	if (lednum > ARRAY_SIZE(wm8350->pmic.led) || lednum < 0) {
> > +		dev_err(wm8350->dev, "Invalid LED index %d\n", lednum);
> > +		return -ENODEV;
> > +	}

> You already used lednum as an array index above, I'm not sure if this
> can have any side effects. I think it shouldn't, as you only use it to
> get a pointer.

It's out of spec to index beyond the end of the array but shouldn't
produce any actual runtime problems unless the either the implementation
or the platform code is being silly.  I'll shuffle the code around,
though.

Fixed everything else.
--
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/