[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zem_0dph7FMwE42u@smile.fi.intel.com>
Date: Thu, 7 Mar 2024 15:23:29 +0200
From: Andy Shevchenko <andy@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Chris Packham <chris.packham@...iedtelesis.co.nz>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
andrew@...n.ch, gregory.clement@...tlin.com,
sebastian.hesselbarth@...il.com, lee@...nel.org,
linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 1/3] auxdisplay: Add 7-segment LED display driver
On Thu, Mar 07, 2024 at 02:13:23PM +0100, Geert Uytterhoeven wrote:
> On Thu, Mar 7, 2024 at 12:50 AM Chris Packham
> <chris.packham@...iedtelesis.co.nz> wrote:
..
> > + DECLARE_BITMAP(values, 8) = { 0 };
While doing next version, drop this '0', as we have in another terminator
the same approach (i.o.w. for the sake of consistency).
..
> > + gpiod_set_array_value_cansleep(priv->segment_gpios->ndescs, priv->segment_gpios->desc,
> > + priv->segment_gpios->info, values);
>
> This may still cause an out-of-bounds access of values if ndescs > 8.
Not really. It will be only for ndescs >= 32 (on 32-bit) or 64
(on 64-bit accordingly).
But good catch, we better to narrow the range down.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists