From: Dan Carpenter <dan.carpenter@oracle.com>
To: aybuke.147@gmail.com
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: staging: iio: accel: Use __be16 instead of u16
Date: Fri, 7 Aug 2015 13:47:18 +0300 [thread overview]
Message-ID: <20150807104718.GH5096@mwanda> (raw)
In-Reply-To: <20150715193650.GA28245@mwanda>
Ping!
regards,
dan carpenter
On Wed, Jul 15, 2015 at 10:36:51PM +0300, Dan Carpenter wrote:
> Hello Aybuke Ozdemir,
>
> The patch 03c6eaa37ad7: "staging: iio: accel: Use __be16 instead of
> u16" from Sep 28, 2014, leads to the following static checker warning:
>
> drivers/staging/iio/accel/sca3000_ring.c:120 sca3000_read_first_n_hw_rb()
> warn: potential pointer math issue ('rx' is a 16 bit pointer)
>
> drivers/staging/iio/accel/sca3000_ring.c
> 107 */
> 108 if (count > num_available * bytes_per_sample)
> 109 num_read = num_available*bytes_per_sample;
> 110 else
> 111 num_read = count;
> 112
> 113 ret = sca3000_read_data(st,
> 114 SCA3000_REG_ADDR_RING_OUT,
> 115 &rx, num_read);
> 116 if (ret)
> 117 goto error_ret;
> 118
> 119 for (i = 0; i < num_read; i++)
> 120 *(((u16 *)rx) + i) = be16_to_cpup((__be16 *)rx + i);
> ^^^^^^^^^^^^^^^
>
> We're writing beyond the end of the array here because of the pointer
> math issue. The fix is probably to say:
>
> for (i = 0; i < num_read / sizeof(u16); i++)
> *(((u16 *)rx) + i) = be16_to_cpup((__be16 *)rx + i);
>
> 121
> 122 if (copy_to_user(buf, rx, num_read))
> 123 ret = -EFAULT;
>
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2015-08-07 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 19:36 staging: iio: accel: Use __be16 instead of u16 Dan Carpenter
2015-08-07 10:47 ` Dan Carpenter [this message]
2015-08-07 10:59 ` Daniel Baluta
2015-08-07 11:27 ` Dan Carpenter
2015-08-07 11:38 ` Lars-Peter Clausen
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=20150807104718.GH5096@mwanda \
--to=dan.carpenter@oracle.com \
--cc=aybuke.147@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.