From: Axel Lin <axel.lin@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/4] regulator/wm831x-dcdc: fix potential NULL dereference
Date: Fri, 20 Aug 2010 23:43:53 +0800 [thread overview]
Message-ID: <AANLkTik-rkJjSD_cH15m6vfvrM_BAd_DfN+Nv5BRK5u3@mail.gmail.com> (raw)
In-Reply-To: <1DE04AB3-1B9A-4962-8A13-AFC74A898D80@opensource.wolfsonmicro.com>
2010/8/20 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> On 20 Aug 2010, at 02:58, Axel Lin <axel.lin@gmail.com> wrote:
>
>> pdata is dereferenced earlier than tested for being NULL.
>> Thus move the dereference of "pdata" below the check for NULL.
>>
>> Signed-off-by: Axel Lin <axel.lin@gmail.com>
>> ---
>> drivers/regulator/wm831x-dcdc.c | 36 ++++++++++++++++++++++++------------
>> 1 files changed, 24 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/regulator/wm831x-dcdc.c b/drivers/regulator/wm831x-dcdc.c
>> index dbfaf59..ed66fac 100644
>> --- a/drivers/regulator/wm831x-dcdc.c
>> +++ b/drivers/regulator/wm831x-dcdc.c
>> @@ -501,14 +501,17 @@ static __devinit int wm831x_buckv_probe(struct platform_device *pdev)
>> {
>> struct wm831x *wm831x = dev_get_drvdata(pdev->dev.parent);
>> struct wm831x_pdata *pdata = wm831x->dev->platform_data;
>> - int id = pdev->id % ARRAY_SIZE(pdata->dcdc);
>
> ARRAY_SIZE() isn't actually a dereference, it's evaluated at compile time.
Ah. You are right! Thanks.
Axel
prev parent reply other threads:[~2010-08-20 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 1:58 [PATCH 1/4] regulator/wm831x-dcdc: fix potential NULL dereference Axel Lin
2010-08-20 1:59 ` [PATCH 2/4] regulator/wm831x-isink: " Axel Lin
2010-08-20 2:01 ` [PATCH 3/4] regulator/wm831x-ldo: " Axel Lin
2010-08-20 2:02 ` [PATCH 4/4] regulator/wm8994-regulator: " Axel Lin
2010-08-20 9:03 ` [PATCH 1/4] regulator/wm831x-dcdc: " Mark Brown
2010-08-20 15:43 ` Axel Lin [this message]
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=AANLkTik-rkJjSD_cH15m6vfvrM_BAd_DfN+Nv5BRK5u3@mail.gmail.com \
--to=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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).