From: Jonathan Cameron <jic23@cam.ac.uk>
To: Grant Grundler <grundler@google.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
devel@linuxdriverproject.org, linux-iio@vger.kernel.org,
bfreed@chromium.org, grundler@chromium.org
Subject: Re: [PATCH] STAGING:iio:light: V2 fix out of bounds reg_cache[] access
Date: Wed, 31 Aug 2011 14:41:11 +0100 [thread overview]
Message-ID: <4E5E39F7.8040203@cam.ac.uk> (raw)
In-Reply-To: <20110830235546.3135B208185@grundler.mtv.corp.google.com>
On 08/31/11 00:55, Grant Grundler wrote:
> V2 Fix out-of-bounds reference to reg_cache[]
>
> Simple fix is to just not cache REG_TEST (offset 8).
> Cache doesn't help REG_TEST anyway since we write all 8 bits exactly once
> (at resume/init time).
>
> Also fix an "off-by-one" allocation of reg_cache[] array size that
> was in the original code before I touched it.
>
Looks good to me. Thanks.
> Reported-by: Dan Carpenter <error27@gmail.com>
> Signed-off-by: Grant Grundler <grundler@chromium.org>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
>
> ----
> Thanks again to Dan Carpenter for spotting the out-of-bounds array reference.
> V2 preserves "don't touch reg_cache[] on error" behavior.
>
> diff --git a/drivers/staging/iio/light/isl29018.c b/drivers/staging/iio/light/isl29018.c
> index 0f97734..b24d28c 100644
> --- a/drivers/staging/iio/light/isl29018.c
> +++ b/drivers/staging/iio/light/isl29018.c
> @@ -51,7 +51,7 @@
>
> #define ISL29018_REG_ADD_DATA_LSB 0x02
> #define ISL29018_REG_ADD_DATA_MSB 0x03
> -#define ISL29018_MAX_REGS ISL29018_REG_ADD_DATA_MSB
> +#define ISL29018_MAX_REGS (ISL29018_REG_ADD_DATA_MSB+1)
>
> #define ISL29018_REG_TEST 0x08
> #define ISL29018_TEST_SHIFT 0
> @@ -71,22 +71,27 @@ struct isl29018_chip {
> static int isl29018_write_data(struct i2c_client *client, u8 reg,
> u8 val, u8 mask, u8 shift)
> {
> - u8 regval;
> - int ret = 0;
> + u8 regval = val;
> + int ret;
> struct isl29018_chip *chip = i2c_get_clientdata(client);
>
> - regval = chip->reg_cache[reg];
> - regval &= ~mask;
> - regval |= val << shift;
> + /* don't cache or mask REG_TEST */
> + if (reg < ISL29018_MAX_REGS) {
> + regval = chip->reg_cache[reg];
> + regval &= ~mask;
> + regval |= val << shift;
> + }
>
> ret = i2c_smbus_write_byte_data(client, reg, regval);
> - if (ret) {
> + if (ret)
> dev_err(&client->dev, "Write to device fails status %x\n", ret);
> - return ret;
> + else {
> + /* don't update cache on err */
> + if (reg < ISL29018_MAX_REGS)
> + chip->reg_cache[reg] = regval;
> }
> - chip->reg_cache[reg] = regval;
>
> - return 0;
> + return ret;
> }
>
> static int isl29018_set_range(struct i2c_client *client, unsigned long range,
next prev parent reply other threads:[~2011-08-31 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 23:55 [PATCH] STAGING:iio:light: V2 fix out of bounds reg_cache[] access Grant Grundler
2011-08-31 13:41 ` Jonathan Cameron [this message]
2011-09-06 23:05 ` Greg KH
2011-09-09 8:53 ` [PATCH] [PATCH] staging:iio:light: V3 " Jonathan Cameron
2011-09-09 8:54 ` Jonathan Cameron
2011-09-09 15:20 ` Grant Grundler
2011-09-09 15:41 ` Jonathan Cameron
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=4E5E39F7.8040203@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=bfreed@chromium.org \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=grundler@chromium.org \
--cc=grundler@google.com \
--cc=linux-iio@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 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).