From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Marek Vasut <marex@denx.de>
Cc: <linux-iio@vger.kernel.org>, Andy Shevchenko <andy@kernel.org>,
"Daniel Baluta" <daniel.baluta@nxp.com>
Subject: Re: [PATCH v2] iio: core: Print error in case sample bits do not fit storage bits
Date: Tue, 22 Mar 2022 21:42:48 +0000 [thread overview]
Message-ID: <20220322214248.00007194@Huawei.com> (raw)
In-Reply-To: <20220322111619.54808-1-marex@denx.de>
On Tue, 22 Mar 2022 12:16:19 +0100
Marek Vasut <marex@denx.de> wrote:
> Add runtime check to verify whether storagebits are at least as big
> as shifted realbits. This should help spot broken drivers which may
> set realbits + shift above storagebits.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Andy Shevchenko <andy@kernel.org>
> Cc: Daniel Baluta <daniel.baluta@nxp.com>
> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Hmm. I was thinking we'd fail the probe if this happens,
though I guess there might be cases where we get away
(in kernel anyway) with a driver setting this wrong as
many drivers don't use realbits internally in an explicit
fashion, so maybe a message and skipping the channel is
the right choice...
Userspace running against such a description is likely
to generate garbage though unless it's very lucky and
the spill past storage bits is into padding space and
the driver doesn't put anything in there (padding might
contain old data or similar).
Either way it's a definite improvement so I'm probably fine
with the message and not failing the probe, (though will
think a bit more about it before picking this up.)
Jonathan`
> ---
> V2: Use dev_err() instead as WARN_ON() may panic() the kernel on existing machines
> ---
> drivers/iio/industrialio-buffer.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
> index b078eb2f3c9de..b5670398b06d7 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
> @@ -1629,6 +1629,18 @@ static int __iio_buffer_alloc_sysfs_and_mask(struct iio_buffer *buffer,
> if (channels[i].scan_index < 0)
> continue;
>
> + /* Verify that sample bits fit into storage */
> + if (channels[i].scan_type.storagebits <
> + channels[i].scan_type.realbits +
> + channels[i].scan_type.shift) {
> + dev_err(&indio_dev->dev,
> + "Channel %d storagebits (%d) < shifted realbits (%d + %d)\n",
> + i, channels[i].scan_type.storagebits,
> + channels[i].scan_type.realbits,
> + channels[i].scan_type.shift);
> + continue;
> + }
> +
> ret = iio_buffer_add_channel_sysfs(indio_dev, buffer,
> &channels[i]);
> if (ret < 0)
next prev parent reply other threads:[~2022-03-22 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 11:16 [PATCH v2] iio: core: Print error in case sample bits do not fit storage bits Marek Vasut
2022-03-22 21:42 ` Jonathan Cameron [this message]
2022-03-23 12:05 ` Nuno Sá
2022-03-27 15:09 ` 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=20220322214248.00007194@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andy@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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