From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"open list" <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org
Cc: "Russell King" <linux@armlinux.org.uk>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Michael Turquette" <mturquette@baylibre.com>
Subject: Re: clkdev: report over-sized strings when creating clkdev entries
Date: Tue, 07 May 2024 09:44:15 +0200 [thread overview]
Message-ID: <11be44d3-0f32-49c6-b4ae-ba97a9f97763@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuZd_ur56H8fwDSvUywopvn_b7ogprGkjEatQ7EPTLwYQ@mail.gmail.com>
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@linaro.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2024-05-07 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+G9fYuZd_ur56H8fwDSvUywopvn_b7ogprGkjEatQ7EPTLwYQ@mail.gmail.com>
2024-05-07 7:44 ` Arnd Bergmann [this message]
2024-05-07 20:26 ` clkdev: report over-sized strings when creating clkdev entries Stephen Boyd
2024-05-07 20:52 ` Arnd Bergmann
2024-05-07 21:55 ` Stephen Boyd
2024-05-08 4:06 ` Anders Roxell
2024-05-08 21:07 ` Sam Protsenko
2024-05-08 22:29 ` Russell King (Oracle)
2024-05-15 20:52 ` Russell King (Oracle)
2024-05-16 10:27 ` Naresh Kamboju
2024-05-16 10:57 ` Marek Szyprowski
2024-05-16 11:33 ` Russell King (Oracle)
2024-05-16 11:32 ` Russell King (Oracle)
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=11be44d3-0f32-49c6-b4ae-ba97a9f97763@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkft-triage@lists.linaro.org \
--cc=mturquette@baylibre.com \
--cc=naresh.kamboju@linaro.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).