From: Jonathan Cameron <jic23@kernel.org>
To: Orson Zhai <orson.zhai@spreadtrum.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: core: Fix suspicious sizeof usage
Date: Thu, 27 Apr 2017 06:32:22 +0100 [thread overview]
Message-ID: <bb016559-2e5b-168f-fdf6-9d127cc3d293@kernel.org> (raw)
In-Reply-To: <1493083016-20571-1-git-send-email-orson.zhai@spreadtrum.com>
On 25/04/17 02:16, Orson Zhai wrote:
> Pointer size is variours in different system, say 32bit for 4 and 64bit
> for 8. The 'sizeof(infomask)' may lead to wrong bit numbers.
>
> Signed-off-by: Orson Zhai <orson.zhai@spreadtrum.com>
That's certainly been there a while. oops.
Anyhow, whilst clearly garbage, it doesn't actually have an effect
at the moment due to the relatively small number of bits that can be
set and the fact this is limited by 32 bit platforms anyway.
So applied to the togreg branch of iio.git and pushed out as
testing for the auto builders to play with it.
Thanks,
Jonathan
> ---
> drivers/iio/industrialio-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index 3ff91e0..795f53c 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -1089,7 +1089,7 @@ static int iio_device_add_info_mask_type(struct iio_dev *indio_dev,
> {
> int i, ret, attrcount = 0;
>
> - for_each_set_bit(i, infomask, sizeof(infomask)*8) {
> + for_each_set_bit(i, infomask, sizeof(*infomask)*8) {
> if (i >= ARRAY_SIZE(iio_chan_info_postfix))
> return -EINVAL;
> ret = __iio_add_chan_devattr(iio_chan_info_postfix[i],
> @@ -1118,7 +1118,7 @@ static int iio_device_add_info_mask_type_avail(struct iio_dev *indio_dev,
> int i, ret, attrcount = 0;
> char *avail_postfix;
>
> - for_each_set_bit(i, infomask, sizeof(infomask) * 8) {
> + for_each_set_bit(i, infomask, sizeof(*infomask) * 8) {
> avail_postfix = kasprintf(GFP_KERNEL,
> "%s_available",
> iio_chan_info_postfix[i]);
>
next prev parent reply other threads:[~2017-04-27 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 1:16 Orson Zhai
2017-04-27 5:32 ` Jonathan Cameron [this message]
2017-04-27 7:29 ` Orson Zhai
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=bb016559-2e5b-168f-fdf6-9d127cc3d293@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orson.zhai@spreadtrum.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®