From: Jonathan Cameron <jic23@kernel.org>
To: David Carlier <devnexen@gmail.com>
Cc: "Ariana Lazar" <ariana.lazar@microchip.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Joshua Crofts" <joshua.crofts1@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] iio: dac: mcp47feb02: reject out-of-range raw values
Date: Sun, 25 Oct 2026 21:57:07 +0000 [thread overview]
Message-ID: <20261025215707.4fe42618@jic23-hlaptop> (raw)
In-Reply-To: <20261025211856.256491-1-devnexen@gmail.com>
On Sun, 25 Oct 2026 21:18:56 +0000
David Carlier <devnexen@gmail.com> wrote:
> mcp47feb02_write_raw() writes the user supplied raw value to the DAC
> register without checking it against the chip resolution. The parts
> are 8, 10 or 12 bit, and the bits above the resolution are not
> implemented, so writing 300 to out_voltage0_raw on an 8-bit part sets
> the output to code 44 instead of failing, and -1 is written as 0xffff.
>
> The out-of-range value is also cached in dac_data, so it is written
> back on resume and stored to EEPROM by store_eeprom.
>
> Return -EINVAL for values outside [0, 2^resolution - 1].
>
> Fixes: bf394cc80369 ("iio: dac: adding support for Microchip MCP47FEB02")
> Cc: stable@vger.kernel.org#
Good catch but given the fix will go in the same cycle as the driver
I've dropped the table tag.
This is more about how I choose to queue this up than anything could
know. I might have held it for next merge window in which case
it would have wanted the stable tag.
Applied to the fixes-togreg branch of iio.git. I've just rebased that
to reflect the char-misc pull going into Linus' tree (which was needed
to get the driver for this patch). I'll rebase again on rc1 once available.
Given I'll be rebasing anyway, extra tags welcome (and I didn't hold
off on applying as I might have done if aiming for no rebasing). Ariana,
please take a look at this one.
Thanks,
Jonathan
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> Found by LLM-assisted code inspection, reviewed and verified by hand.
> Build tested with W=1 (=m and =y) only; no hardware was available for
> runtime testing.
>
> v2:
> - Use GENMASK() for the upper bound so it is safe up to 32 bits (Andy)
> - Drop the Assisted-by tag, removed from the docs in 1e035297ffda (Joshua)
> - Move the testing note below the --- (Joshua)
>
> v1: https://lore.kernel.org/all/20261024214423.865635-1-devnexen@gmail.com/
> ---
> drivers/iio/dac/mcp47feb02-core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/dac/mcp47feb02-core.c b/drivers/iio/dac/mcp47feb02-core.c
> index 88bffbab0854..b5a2ac4a2e67 100644
> --- a/drivers/iio/dac/mcp47feb02-core.c
> +++ b/drivers/iio/dac/mcp47feb02-core.c
> @@ -696,6 +696,9 @@ static int mcp47feb02_write_raw(struct iio_dev *indio_dev, struct iio_chan_spec
>
> switch (mask) {
> case IIO_CHAN_INFO_RAW:
> + if (val < 0 || val > GENMASK(data->chip_features->resolution - 1, 0))
> + return -EINVAL;
> +
> ret = regmap_write(data->regmap, REG_ADDR(ch->address), val);
> if (ret)
> return ret;
prev parent reply other threads:[~2026-10-25 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 21:18 David Carlier
2026-10-25 21:36 ` Andy Shevchenko
2026-10-25 21:57 ` 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=20261025215707.4fe42618@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=devnexen@gmail.com \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stable@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
all inboxes | Powered by JetHome®