Received-SPF: pass (google.com: domain of linux-kernel+bounces-46432-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Wed, 31 Jan 2024 12:42:45 +0000
From: Mark Brown <broonie@kernel.org>
To: Daniel =?iso-8859-1?Q?D=EDaz?= <daniel.diaz@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org, linux-stable <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Marc Zyngier <maz@kernel.org>
Subject: Re: selftests: ftrace: Internal error: Oops: sve_save_state
Message-ID: <1b3064d0-d41d-414a-85ad-5202a089ad5e@sirena.org.uk>
References: <CA+G9fYtEGe_DhY2Ms7+L7NKsLYUomGsgqpdBj+QwDLeSg=JhGg@mail.gmail.com>
 <ad5b7442-385d-41db-9202-a36414460610@sirena.org.uk>
 <CA+G9fYsbwWpDVR9KJXx8UO5MXsYT81uAJbLLNDnLianr8jmXUA@mail.gmail.com>
 <63e92a6a-9cb7-4272-b524-ccaf997aceb3@sirena.org.uk>
 <CAEUSe7_9tE5K7NpsmaG_v_bTJaMGhVVSDRhMn1QYnr2z4vSg8w@mail.gmail.com>
 <b1b8cbdd-6d6c-4656-b17a-4d2dfb555f8a@sirena.org.uk>
 <787d3fb1-7aad-4e92-8a22-360b92f46c68@linaro.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="LcSh5X4TdHiaSEzi"
Content-Disposition: inline
In-Reply-To: <787d3fb1-7aad-4e92-8a22-360b92f46c68@linaro.org>


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

On Tue, Jan 30, 2024 at 06:15:11PM -0600, Daniel D=EDaz wrote:

> > That's an assert that we shouldn't take a SVE trap when SVE is
> > alreadly enabled for the thread.  The backtrace Naresh originally
> > supplied was a NULL pointer dereference attempting to save SVE state

=2E..

> > given.  Can you double check exactly how similar the various issues you
> > are seeing are please?

> I'm not sure of how similar the test cases are, but I'm inclined to
> think its occurrence is not related specifically to ftrace or one test
> case. It looks like these appear on FVP and Qemu-arm64, on several LTS

That question is not about the test that is running, that question is
about the error that the kernel reports.  There were two different but
potentially related kernel errors in the reports that you and Naresh
sent, I'm asking how similar the other cases actually are - is it more
instances of these two issues, are there possibly other issues?

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmW6QEQACgkQJNaLcl1U
h9D88wf8Cb366GwwKV1HpvWfjvF6pI3NDFA3D1AMxUuPrRD6QTrKVnsJOCyz2pdX
WKAuINE8bLazLTUL+F7UhHH0wZj2DcwLeH8Zu93OAfM824aVAAUqVKQxigL01VnX
q4FAip2FZUwQLGPnViIeT5RA8wne4RHvcUrxIjHSeQvPCiK2NgMHynQl4h6MsDIe
1lIn3OUDXW+GSt7gcndvGkoAxayb0tLMrPcr3+nwEDj8OhMog/H3YQ6TygLSZg50
5Ayq3GHGsA7A+3wABc1zmA+aaapDCoM2Hj4gbEQrpGEA2YaSud8FGG7OQ4Zv5zzn
hHa1zWevvdrzvtejMvX096LcjSTlWA==
=JsX4
-----END PGP SIGNATURE-----

--LcSh5X4TdHiaSEzi--