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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220622071151.xmabagjyr5qasff5@pengutronix.de>
Date:   Wed, 22 Jun 2022 09:11:51 +0200
From:   Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        linux-clk <linux-clk@...r.kernel.org>,
        regressions@...ts.linux.dev, lkft-triage@...ts.linaro.org,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Alexandru Ardelean <aardelean@...iqon.com>,
        Wolfram Sang <wsa+renesas@...g-engineering.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
        Peng Fan <peng.fan@....com>
Subject: Re: [next] Unable to handle kernel execute from non-executable
 memory at virtual address - devm_clk_release

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@...aro.org>
> 
> 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@pengutronix.de/

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.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)