From: Jonathan Cameron <jic23@kernel.org>
To: Nikhil Gautam <nikhilgtr@gmail.com>
Cc: anshulusr@gmail.com, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: chemical: ags02ma: Check for short I2C reads
Date: Sat, 17 Oct 2026 19:18:12 +0100 [thread overview]
Message-ID: <20261017191757.0e18754f@jic23-hlaptop> (raw)
In-Reply-To: <20261017094639.3002-1-nikhilgtr@gmail.com>
On Sat, 17 Oct 2026 15:16:39 +0530
Nikhil Gautam <nikhilgtr@gmail.com> wrote:
> Check that the I2C receive operation transfers the expected number
> of bytes before accessing the received data.
>
> Return -EIO if the transfer is incomplete.
>
> Fixes: d58013f39b30 ("iio: chemical: add support for Aosong AGS02MA")
> Signed-off-by: Nikhil Gautam <nikhilgtr@gmail.com>
Hi Nikhil,
Given in practice we are very unlikely to ever see this condition I've
not rushed this one in. Next cycle is soon enough.
As such, applied to the testing branch of iio.git.
Jonathan
> ---
> drivers/iio/chemical/ags02ma.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/iio/chemical/ags02ma.c b/drivers/iio/chemical/ags02ma.c
> index 151178d4e8f4..2219965d044f 100644
> --- a/drivers/iio/chemical/ags02ma.c
> +++ b/drivers/iio/chemical/ags02ma.c
> @@ -61,6 +61,12 @@ static int ags02ma_register_read(struct i2c_client *client, u8 reg, u16 delay,
> return ret;
> }
>
> + if (ret != sizeof(read_buffer)) {
> + dev_err(&client->dev,
> + "Short read from register 0x%x\n", reg);
> + return -EIO;
> + }
> +
> crc = crc8(ags02ma_crc8_table, (u8 *)&read_buffer.data,
> sizeof(read_buffer.data), AGS02MA_CRC8_INIT);
> if (crc != read_buffer.crc) {
prev parent reply other threads:[~2026-10-17 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 9:46 Nikhil Gautam
2026-10-17 18:18 ` Jonathan Cameron [this message]
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=20261017191757.0e18754f@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=anshulusr@gmail.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhilgtr@gmail.com \
--cc=nuno.sa@analog.com \
/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®