[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <11be44d3-0f32-49c6-b4ae-ba97a9f97763@app.fastmail.com>
Date: Tue, 07 May 2024 09:44:15 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Naresh Kamboju" <naresh.kamboju@...aro.org>,
"open list" <linux-kernel@...r.kernel.org>,
linux-clk <linux-clk@...r.kernel.org>,
"Linux ARM" <linux-arm-kernel@...ts.infradead.org>,
lkft-triage@...ts.linaro.org
Cc: "Russell King" <linux@...linux.org.uk>,
"Anders Roxell" <anders.roxell@...aro.org>,
"Dan Carpenter" <dan.carpenter@...aro.org>,
"Michael Turquette" <mturquette@...libre.com>
Subject: Re: clkdev: report over-sized strings when creating clkdev entries
On Tue, May 7, 2024, at 09:20, Naresh Kamboju wrote:
> The WinLink E850-96 board boot failed with Linux next-20240506 but there
> is no kernel crash log on the serial [1].
>
> Anders bisection results pointing to this commit,
> # first bad commit:
> [4d11c62ca8d77cb1f79054844b598e0f4e92dabe]
> clkdev: report over-sized strings when creating clkdev entrie
>
> After reverting the above patch the boot test passed [2].
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> Links:
> [1] - https://lkft.validation.linaro.org/scheduler/job/7546260
> [2] - https://lkft.validation.linaro.org/scheduler/job/7548064
I assume this is an actual overflow that was previously ignored
and is now causing vclkdev_alloc() to fail. Unfortunately this
happens before the console is up, so there is no output. Can
you run the broken version again with 'earlycon' added to the
boot arguments?
Arnd
Powered by blists - more mailing lists