Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 22 Jun 2022 09:11:51 +0200
From:   Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>
To:     Naresh Kamboju <naresh.kamboju@linaro.org>
Cc:     Linux-Next Mailing List <linux-next@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>,
        linux-clk <linux-clk@vger.kernel.org>,
        regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Michael Turquette <mturquette@baylibre.com>,
        Stephen Boyd <sboyd@kernel.org>,
        Jonathan Cameron <Jonathan.Cameron@huawei.com>,
        Alexandru Ardelean <aardelean@deviqon.com>,
        Wolfram Sang <wsa+renesas@sang-engineering.com>,
        Geert Uytterhoeven <geert+renesas@glider.be>,
        Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
        Peng Fan <peng.fan@nxp.com>
Subject: Re: [next] Unable to handle kernel execute from non-executable
 memory at virtual address - devm_clk_release
Message-ID: <20220622071151.xmabagjyr5qasff5@pengutronix.de>
References: <CA+G9fYv4S2TqZ53oH5FEK07qHV+LwkZEx7+KNiCa5wZWruDSfA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="lqt3bo3e3asngv5g"
Content-Disposition: inline
In-Reply-To: <CA+G9fYv4S2TqZ53oH5FEK07qHV+LwkZEx7+KNiCa5wZWruDSfA@mail.gmail.com>
Precedence: bulk


--lqt3bo3e3asngv5g
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>=20
> 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/-/pip=
elines/567830223
>   artifact-location: https://builds.tuxbuild.com/2ApqivCh2DP6v2QxI17B2GnW=
iUk
>   toolchain: gcc-11

Patch available at https://lore.kernel.org/all/20220620171815.114212-1-u.kl=
eine-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

--=20
Pengutronix e.K.                           | Uwe Kleine-K=F6nig            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

--lqt3bo3e3asngv5g
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAmKywLQACgkQwfwUeK3K
7AleAgf+JZg7IG3GJ2dkcv/k61X0tlqdukxR0hKi2O69G3gOTAy/nWRvoJNfizdj
T77eaizrdrfpqU2hpjsjd2XCiW5USzUItWtvhwC2BOZFqhvWYizrbt1GC922lf0Y
u48Jf3b7de0Ft4KgaCAAGWB5F4GvU8qP9tMNLlx57ojiO6my7Inwlef4gJ7sRkpt
UUDX+3uMQRbWT7n6IcLvcKtKPobuyZmmt0S7IRjyeanrWOT96Nz9OodBnwb/82VG
vppCQ+bhilNUSHDpQIVyqiCvrD3aPMG8+rffdczKVPe9iW/nWlV7W6ZCF4MYDcB3
q9VWq/HxAc7IUoH1g/yWXWKSXcmGlQ==
=b4NL
-----END PGP SIGNATURE-----

--lqt3bo3e3asngv5g--