From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v6 2/8] iio: core: add fixed point parsing with 64-bit parts
Date: Wed, 4 Feb 2026 11:57:58 +0200 [thread overview]
Message-ID: <aYMYJppigidPeLH4@smile.fi.intel.com> (raw)
In-Reply-To: <7tiv33i65unu5ypk7puj3buzybykyhv2qbwp54bhcem5t4rawq@dpfedqmmxbhx>
On Wed, Feb 04, 2026 at 09:42:55AM +0000, Rodrigo Alencar wrote:
> On 26/02/04 03:45AM, Andy Shevchenko wrote:
> > On Fri, Jan 30, 2026 at 10:06:43AM +0000, Rodrigo Alencar via B4 Relay wrote:
...
> > > +static ssize_t iio_safe_strntou64(const char *str, const char **endp,
> > > + u64 *result, size_t max_chars)
> > > +{
> > > + u64 digit, acc = 0;
> > > + ssize_t idx = 0;
> > > +
> > > + while (isdigit(str[idx]) && idx < max_chars) {
> > > + digit = str[idx] - '0';
> > > + if (unlikely(acc & (~0ull << 60))) {
> > > + if (check_mul_overflow(acc, 10, &acc) ||
> > > + check_add_overflow(acc, digit, &acc))
> > > + return -ERANGE;
> > > + } else {
> > > + acc = acc * 10 + digit;
> > > + }
> > > + idx++;
> > > + }
> > > +
> > > + *endp = str + idx;
> > > + *result = acc;
> > > + return idx;
> > > +}
> >
> > There is a development in the parse_integer in the lib/. I reviewed that series
> > and hopefully it will go in. With that done, we better reuse the lib/ function.
> >
> > https://lore.kernel.org/linux-hardening/20260202115451.290173-1-dmantipov@yandex.ru/
>
> In this patch, I see that it updates the overflow check, but I am not
> seeing that function being exposed to other kernel modules.
Can the IIO be compiled as a module? If so, then we would need to export that
function. (Note, we may export only for the exact module(s) in question, so
nobody else will be able to use it. See EXPORT_SYMBOL_FOR_MODULES() macro.)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-04 9:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 10:06 [PATCH v6 0/8] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 1/8] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 2/8] iio: core: add fixed point parsing with 64-bit parts Rodrigo Alencar via B4 Relay
2026-02-02 9:57 ` Nuno Sá
2026-02-03 9:26 ` Rodrigo Alencar
2026-02-03 10:04 ` Nuno Sá
2026-02-07 16:59 ` Jonathan Cameron
2026-02-04 1:45 ` Andy Shevchenko
2026-02-04 9:42 ` Rodrigo Alencar
2026-02-04 9:57 ` Andy Shevchenko [this message]
2026-02-04 10:28 ` Rodrigo Alencar
2026-02-04 10:34 ` Andy Shevchenko
2026-02-07 17:02 ` Jonathan Cameron
2026-02-08 13:24 ` Andy Shevchenko
2026-01-30 10:06 ` [PATCH v6 3/8] iio: test: add kunit test for fixed-point parsing Rodrigo Alencar via B4 Relay
2026-02-03 15:38 ` Andy Shevchenko
2026-01-30 10:06 ` [PATCH v6 4/8] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2026-02-07 17:21 ` Jonathan Cameron
2026-01-30 10:06 ` [PATCH v6 5/8] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 6/8] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 7/8] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 8/8] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar via B4 Relay
2026-02-07 17:24 ` Jonathan Cameron
2026-02-11 13:52 ` Rodrigo Alencar
2026-02-14 14:44 ` 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=aYMYJppigidPeLH4@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@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