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:   Tue, 23 May 2023 11:49:38 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Will Deacon <will@kernel.org>
Cc:     Naresh Kamboju <naresh.kamboju@linaro.org>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@vger.kernel.org>,
        linux-stable <stable@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>,
        lkft-triage@lists.linaro.org,
        Catalin Marinas <catalin.marinas@arm.com>,
        Dan Carpenter <dan.carpenter@linaro.org>,
        Arnd Bergmann <arnd@arndb.de>, Shuah Khan <shuah@kernel.org>,
        Anders Roxell <anders.roxell@linaro.org>
Subject: Re: arm64: fp-stress: BUG: KFENCE: memory corruption in
 fpsimd_release_task
Message-ID: <a174b99c-3b60-410d-b6b3-67e8e792354c@sirena.org.uk>
References: <CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com>
 <20230516134447.GB30894@willie-the-truck>
 <20230522164117.GA6342@willie-the-truck>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="0WyD5qb6h9pTGLPu"
Content-Disposition: inline
In-Reply-To: <20230522164117.GA6342@willie-the-truck>
Precedence: bulk


--0WyD5qb6h9pTGLPu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, May 22, 2023 at 05:41:17PM +0100, Will Deacon wrote:
> On Tue, May 16, 2023 at 02:44:49PM +0100, Will Deacon wrote:
> > On Tue, May 16, 2023 at 11:58:40AM +0530, Naresh Kamboju wrote:

> > > Following kernel BUG noticed while running selftests arm64 fp-stress
> > > running stable rc kernel versions 6.1.29-rc1 and 6.3.3-rc1.

> > Is there a known-good build so that we could attempt a bisection?

> FWIW, I've been trying (and failing) all day to reproduce this in QEMU.
> I matched the same VL configuration as you have in the fastmodel and
> tried enabling additional memory debugging options too, but I'm yet to
> see a kfence splat (or any other splat fwiw).

> How often do you see this?

As I said in another mail I've also been unable to reproduce this.  FWIW
I *suspect* that it might need to be run in the context of a full
kselftest run to manifest rather than just running fp-stress in
isolation, that's mostly a guess but given that the kfence trap appeared
to be happening on free at a point where the test program shouldn't be
exiting any tasks and should not be changing vector lengths on tasks
that have used either of the vector extensions.

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmRsmkIACgkQJNaLcl1U
h9BhWAgAgmrfoTxlzsDDX+RDl6E01tBdBvmcEH5N6AgAWSJaMNjla/SYW31Pgos0
ArDjoqjfyIskP+UZ6T5UXrKxOe1rSaN6fwOovNCiyE+FIZ28Ml6cfp96YM/ElXGH
DrjHKAelYRTaZndLBq5aNmDGO1A6Fz2w4t0Y/5vUnF6X4dWKo/8udixbbMNPe551
NWehZoHz9eFNFPop3UDJKQPjZDDA0/LP6yBoAhsSN2ySzt1SuQBrO+NxpHqOA3ZD
KM5BVVJq51ZQ9FNR8TbylrB7lWkHoR9fDXnM6ukbCNy+giOa1lvDJyDHxMiKxQ6b
hBi7UdqunNL69HmnoS8jKoS0r0CBEQ==
=RfVs
-----END PGP SIGNATURE-----

--0WyD5qb6h9pTGLPu--