From: David Lechner <dlechner@baylibre.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>, linux-iio@vger.kernel.org
Cc: "Gyeyoung Baek" <gye976@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: chemical: mhz19b: bound receive buffer copy
Date: Sun, 22 Mar 2026 09:34:24 -0500 [thread overview]
Message-ID: <b90be3d0-1372-4ace-8e7c-aeab1ff60815@baylibre.com> (raw)
In-Reply-To: <20260322134807.16217-1-pengpeng@iscas.ac.cn>
On 3/22/26 8:48 AM, Pengpeng Hou wrote:
> `mhz19b_receive_buf()` appends bytes to the fixed 9-byte command buffer
> without first checking that the new chunk fits in the remaining space.
> A single receive callback can therefore write past the end of `st->buf`
> before the driver sees that the command is complete.
>
> Drop overlong chunks and reset the partial command state before the
> copy.
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
Please don't make v2 a reply to v1. It makes it hard to see that a new
version has been sent. Also, please include a changelog here (below the
---) when sending new revisions so that we know what changed compared
to v1.
For this patch, you can just reply with the changelog instead of sending
a new revision.
Also, you received an Acked-by on v1, so you need to explain why you did
not keep that tag when you sent v2.
> drivers/iio/chemical/mhz19b.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/iio/chemical/mhz19b.c b/drivers/iio/chemical/mhz19b.c
> index 3c64154918b1..fbd7f14483b3 100644
> --- a/drivers/iio/chemical/mhz19b.c
> +++ b/drivers/iio/chemical/mhz19b.c
> @@ -240,6 +240,12 @@ static size_t mhz19b_receive_buf(struct serdev_device *serdev,
> {
> struct iio_dev *indio_dev = dev_get_drvdata(&serdev->dev);
> struct mhz19b_state *st = iio_priv(indio_dev);
> + size_t remaining = sizeof(st->buf) - st->buf_idx;
> +
> + if (unlikely(len > remaining)) {
> + st->buf_idx = 0;
> + return len;
> + }
>
> memcpy(st->buf + st->buf_idx, data, len);
> st->buf_idx += len;
next prev parent reply other threads:[~2026-03-22 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 3:19 [PATCH] " Pengpeng Hou
2026-03-22 11:52 ` Gyeyoung Baek
2026-03-22 13:48 ` [PATCH v2] " Pengpeng Hou
2026-03-22 14:34 ` David Lechner [this message]
2026-04-12 15:12 ` Jonathan Cameron
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=b90be3d0-1372-4ace-8e7c-aeab1ff60815@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=gye976@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pengpeng@iscas.ac.cn \
/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®