Re: next/master baseline: 539 runs, 389 regressions (next-20220920)

[Fabio Estevam <festevam@xxxxxxxxx>]

Hi Guillaume,

On Wed, Sep 21, 2022 at 6:18 AM Guillaume Tucker
<guillaume.tucker@xxxxxxxxxxxxx> wrote:
>
> On 21/09/2022 04:48, Fabio Estevam wrote:
> > Hi,
> >
> > On Tue, Sep 20, 2022 at 3:48 PM kernelci.org bot <bot@xxxxxxxxxxxx> wrote:
> >>
> >> next/master baseline: 539 runs, 389 regressions (next-20220920)
> >
> > Does anyone know which commit caused such a massive regression?
> >
> > Looks like it is gpiod_get_index related.
>
> There's a bisection report, does it look like it?

Sorry, I missed the git-bisect results in the original email.

Just noticed a fix for this problem on today's linux-next, so we are
all good, thanks:

commit 8b10ca2f7551e024b60ab5e27d3e3630c029000a
Author: Michael Walle <michael@xxxxxxxx>
Date:   Fri Sep 16 13:01:18 2022 +0200

    gpiolib: fix OOB access in quirk callbacks

    Commit a2b5e207cade ("gpiolib: rework quirk handling in of_find_gpio()")
    introduced an array of quirk functions which get iterated over. But a
    sentinal value is missing. Add it.

    Fixes: a2b5e207cade ("gpiolib: rework quirk handling in of_find_gpio()")
    Signed-off-by: Michael Walle <michael@xxxxxxxx>
    Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
    Tested-by: Conor Dooley <conor.dooley@xxxxxxxxxxxxx>
    Reviewed-by: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
    Tested-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
    Tested-by: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
    Signed-off-by: Bartosz Golaszewski <brgl@xxxxxxxx>