Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 6 Oct 2020 17:39:43 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Jeremy Linton <jeremy.linton@arm.com>
Cc:     linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org,
        ardb@kernel.org, will@kernel.org, catalin.marinas@arm.com,
        davem@davemloft.net, herbert@gondor.apana.org.au,
        linux-kernel@vger.kernel.org, dave.martin@arm.com
Subject: Re: [BUG][PATCH v3] crypto: arm64: Use x16 with indirect branch to
 bti_c
Message-ID: <20201006163943.GD5259@sirena.org.uk>
References: <20201006163326.2780619-1-jeremy.linton@arm.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="6Nae48J/T25AfBN4"
Content-Disposition: inline
In-Reply-To: <20201006163326.2780619-1-jeremy.linton@arm.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk


--6Nae48J/T25AfBN4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Oct 06, 2020 at 11:33:26AM -0500, Jeremy Linton wrote:
> The AES code uses a 'br x7' as part of a function called by
> a macro. That branch needs a bti_j as a target. This results
> in a panic as seen below. Using x16 (or x17) with an indirect
> branch keeps the target bti_c.

Reviewed-by: Mark Brown <broonie@kernel.org>

--6Nae48J/T25AfBN4
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl98nc4ACgkQJNaLcl1U
h9CLAwf9FiPQZ/xkGSQroau0bLLgKubdsRTXCnzajbWymLdZcF7NPVkEqC61rY+X
hTAWXCf2S9EtKxSV93rO0ea9HsRomillICgvVTDfk0tn4AOz8d60dTNtMaMuwQZ4
qlOxUBnkMk1XL4QoOiY5X8G9APy/sEIcZas0GqobABxmnRA1DduxLQtfF5x0BRoO
BKhSQ2v3nHThDpOJ5ati6KAq3R3IdAtgzPt02Y6K28RXRXktAUbtcPJFMMCEWPox
XylPKGq4FGqFWGEoeGAdf+6vcT3v1A40fSp9WvX94RO43YuJfJhSjwUVcDApiXSX
BVagPfdEIahk4NrD2q4kDgQW3Z7Tsg==
=eHIP
-----END PGP SIGNATURE-----

--6Nae48J/T25AfBN4--