From: Jonathan Cameron <jic23@kernel.org>
To: Haowen Bai <baihaowen@meizu.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] iio: gp2ap020a00f: Fix signedness bug
Date: Thu, 28 Apr 2022 19:41:32 +0100 [thread overview]
Message-ID: <20220428194132.5a02555c@jic23-huawei> (raw)
In-Reply-To: <1650248375-6334-1-git-send-email-baihaowen@meizu.com>
On Mon, 18 Apr 2022 10:19:35 +0800
Haowen Bai <baihaowen@meizu.com> wrote:
> function gp2ap020a00f_get_thresh_reg() is unsigned but returning -EINVAL
> errcode, and thresh_reg_l is unsigned but receiving -EINVAL errcode. so
> we have to change u8 -> int. Also we need to do index bound check at
> gp2ap020a00f_read_event_val().
>
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
Please add a Fixes tag if possible.
> ---
> V1->V2: s8 is not enough to hold an (arbitrary) error code. To be on the safe
> side we need to use int.
> V2->V3: add bound check at gp2ap020a00f_read_event_val().
>
>
> drivers/iio/light/gp2ap020a00f.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/light/gp2ap020a00f.c b/drivers/iio/light/gp2ap020a00f.c
> index b820041159f7..f80d30786035 100644
> --- a/drivers/iio/light/gp2ap020a00f.c
> +++ b/drivers/iio/light/gp2ap020a00f.c
> @@ -994,7 +994,7 @@ static irqreturn_t gp2ap020a00f_trigger_handler(int irq, void *data)
> return IRQ_HANDLED;
> }
>
> -static u8 gp2ap020a00f_get_thresh_reg(const struct iio_chan_spec *chan,
> +static int gp2ap020a00f_get_thresh_reg(const struct iio_chan_spec *chan,
> enum iio_event_direction event_dir)
> {
> switch (chan->type) {
> @@ -1025,7 +1025,7 @@ static int gp2ap020a00f_write_event_val(struct iio_dev *indio_dev,
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> bool event_en = false;
> u8 thresh_val_id;
> - u8 thresh_reg_l;
> + int thresh_reg_l;
You need to check this val after the function call, but before it is used.
> int err = 0;
>
> mutex_lock(&data->lock);
> @@ -1082,14 +1082,14 @@ static int gp2ap020a00f_read_event_val(struct iio_dev *indio_dev,
> int *val, int *val2)
> {
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> - u8 thresh_reg_l;
> + int thresh_reg_l;
> int err = IIO_VAL_INT;
>
> mutex_lock(&data->lock);
>
> thresh_reg_l = gp2ap020a00f_get_thresh_reg(chan, dir);
>
> - if (thresh_reg_l > GP2AP020A00F_PH_L_REG) {
> + if (thresh_reg_l < 0 || thresh_reg_l > GP2AP020A00F_PH_L_REG) {
> err = -EINVAL;
If a function returns an error we should pass that on unchanged
Here the value is the same, but none the less we should have this look something
like.
if (thresh_reg_l < 0)
return thresh_reg_l;
if (thresh_reg_l > GP2AP020A00F_PH_L_REG)
...
> goto error_unlock;
> }
next prev parent reply other threads:[~2022-04-28 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 10:45 [PATCH] iio: gp2ap020a00f: Fix signedness bug Haowen Bai
2022-04-14 13:47 ` Andy Shevchenko
2022-04-15 1:20 ` [PATCH V2] " Haowen Bai
2022-04-15 17:52 ` Jonathan Cameron
2022-04-18 2:19 ` [PATCH V3] " Haowen Bai
2022-04-28 18:41 ` Jonathan Cameron [this message]
2022-04-29 1:36 ` [PATCH V4] " Haowen Bai
2022-05-01 15:03 ` Jonathan Cameron
2022-04-18 2:20 ` [PATCH V2] " baihaowen
2022-04-15 1:21 ` [PATCH] " baihaowen
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=20220428194132.5a02555c@jic23-huawei \
--to=jic23@kernel.org \
--cc=baihaowen@meizu.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).