From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Cosmin Tanislav <cosmin.tanislav@analog.com>
Subject: Re: [PATCH] iio:addac:ad74413r: Fix uninitialized ret in a path that won't be hit.
Date: Mon, 20 Dec 2021 16:51:13 +0000 [thread overview]
Message-ID: <20211220165114.7e7af8b9@jic23-huawei> (raw)
In-Reply-To: <20211220164726.3136307-1-jic23@kernel.org>
On Mon, 20 Dec 2021 16:47:26 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> I don't believe it's possible to hit this, because we drop
> out of __iio_update_buffers() earlier in the event of an empty
> list. However, that is not visible to the compiler so lets
> return an error if we do hit the loop with an empty bitmask.
>
> Fixes: 5d97d9e9a703 ("iio: addac: ad74413r: fix off by one in ad74413r_parse_channel_config()")
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Cosmin Tanislav <cosmin.tanislav@analog.com>
Given this is 'hopefully' entirely safe and I'd like to get a pull
request out later in the week I'm going to apply this immediately.
Note I'd have just fixed it up in the original patch normally but for
some reason didn't see the warning until the tree was in a non rebasing
state + we have some other fixes in there for this driver.
Applied to the togreg branch of iio.git. Pushed out directly rather than
normal testing. I'll sneak a rebase in if anyone gives me a tag
before I apply much on top of it.
Thanks,
Jonathan
> ---
> drivers/iio/addac/ad74413r.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/addac/ad74413r.c b/drivers/iio/addac/ad74413r.c
> index 289d254943e1..5271073bb74e 100644
> --- a/drivers/iio/addac/ad74413r.c
> +++ b/drivers/iio/addac/ad74413r.c
> @@ -843,7 +843,7 @@ static int ad74413r_update_scan_mode(struct iio_dev *indio_dev,
> u8 *rx_buf = &st->adc_samples_buf.rx_buf[-1 * AD74413R_FRAME_SIZE];
> u8 *tx_buf = st->adc_samples_tx_buf;
> unsigned int channel;
> - int ret;
> + int ret = -EINVAL;
>
> mutex_lock(&st->lock);
>
next prev parent reply other threads:[~2021-12-20 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:47 [PATCH] iio:addac:ad74413r: Fix uninitialized ret in a path that won't be hit Jonathan Cameron
2021-12-20 16:51 ` Jonathan Cameron [this message]
2021-12-21 13:20 ` Cai Huoqing
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=20211220165114.7e7af8b9@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=cosmin.tanislav@analog.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