Re: [next] Unable to handle kernel execute from non-executable memory at virtual address - devm_clk_release

[Naresh Kamboju]

On Wed, 22 Jun 2022 at 12:42, Uwe Kleine-König
<u.kleine-koenig@xxxxxxxxxxxxxx> wrote:
>
> On Wed, Jun 22, 2022 at 06:41:30AM +0530, Naresh Kamboju wrote:
> > The following kernel crash was noticed on arm64 Raspberry Pi 4 Model B
> > devices while booting. This crash is always reproducible.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>
> >
> > metadata:
> >   git_ref: master
> >   git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> >   git_sha: 1e502319853ceebfe7480a436ba22ab01372fa0c
> >   git_describe: next-20220620
> >   kernel_version: 5.19.0-rc3
> >   kernel-config: https://builds.tuxbuild.com/2ApqivCh2DP6v2QxI17B2GnWiUk/config
> >   build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/567830223
> >   artifact-location: https://builds.tuxbuild.com/2ApqivCh2DP6v2QxI17B2GnWiUk
> >   toolchain: gcc-11
>
> Patch available at https://lore.kernel.org/all/20220620171815.114212-1-u.kleine-koenig@xxxxxxxxxxxxxx/

I have tested your patch and the reported issues got fixed.
Tested-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>

> I wonder how the recipents of this mail were choosen. If your build bot
> identified abae8e57e49aa75f6db76aa866c775721523908f as the broken
> commit, this would be a very helpful information in this report.

We are working on improving our tooling for test bisection
and reporting emailers.

- Naresh