Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
To:     "Ben Dooks (Codethink)" <ben.dooks@codethink.co.uk>,
        "linux-kernel@lists.codethink.co.uk" 
        <linux-kernel@lists.codethink.co.uk>
CC:     Antoine Tenart <antoine.tenart@bootlin.com>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        "David S. Miller" <davem@davemloft.net>,
        "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] crypto: inside-secure - fix type of buffer in
 eip197_write_firmware
Thread-Topic: [PATCH] crypto: inside-secure - fix type of buffer in
 eip197_write_firmware
Thread-Index: AQHVhBfWMp/OQ1W3YkiqzB+SEDRBb6dfDogAgAAvRhA=
Date:   Thu, 17 Oct 2019 19:46:21 +0000
Message-ID: <MN2PR20MB2973592C6237B840BC63B71ACA6D0@MN2PR20MB2973.namprd20.prod.outlook.com>
References: <20191016114945.30451-1-ben.dooks@codethink.co.uk> 
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: verimatrix.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dc2b18a1-3102-40a9-92a0-08d7533ab08e
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Oct 2019 19:46:22.5250
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dcb260f9-022d-4495-8602-eae51035a0d0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: AygHh9atVGNV3UOdDiX8dmTHLUuiy+Ukvyj9hUNcbcZExW0c/Z8w84UgnZbb8I/61drJicO+Wuq7SxBBqvyW3jXcJVO6ilQp5i5FMtBoKBI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR20MB2639
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> -----Original Message-----
> From: Pascal Van Leeuwen
> Sent: Thursday, October 17, 2019 7:14 PM
> To: 'Ben Dooks (Codethink)' <ben.dooks@codethink.co.uk>; linux-
> kernel@lists.codethink.co.uk
> Cc: Antoine Tenart <antoine.tenart@bootlin.com>; Herbert Xu
> <herbert@gondor.apana.org.au>; David S. Miller <davem@davemloft.net>; lin=
ux-
> crypto@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: RE: [PATCH] crypto: inside-secure - fix type of buffer in eip197=
_write_firmware
>=20
> > -----Original Message-----
> > From: linux-crypto-owner@vger.kernel.org <linux-crypto-owner@vger.kerne=
l.org> On Behalf
> Of Ben
> > Dooks (Codethink)
> > Sent: Wednesday, October 16, 2019 1:50 PM
> > To: linux-kernel@lists.codethink.co.uk
> > Cc: Ben Dooks (Codethink) <ben.dooks@codethink.co.uk>; Antoine Tenart
> > <antoine.tenart@bootlin.com>; Herbert Xu <herbert@gondor.apana.org.au>;=
 David S. Miller
> > <davem@davemloft.net>; linux-crypto@vger.kernel.org; linux-kernel@vger.=
kernel.org
> > Subject: [PATCH] crypto: inside-secure - fix type of buffer in eip197_w=
rite_firmware
> >
> > In eip197_write_firmware() the firmware buffer is sent using
> > writel(be32_to_cpu(),,,) this produces a number of warnings.
> >
> > Note, should this really be cpu_to_be32()  ?
> >
> No, it should certainly not be cpu_to_be32() since the HW itself is most
> definitely little endian, so that would not make sense to me.
>=20
> Actually, I don't think either solution would be correct on a big-endian
> CPU. But I don't have any big-endian CPU available to test that theory.
>=20
> What I believe must happen is that the bytes must *always* be swapped
> here, regardless of the endianness of the CPU. And with a little-endian
> CPU, be32_to_cpu() coincidentally always does that.
>=20
> Basically, what we need here is: read a dword (32 bits) from the memory
> subsystem and write it back to the memory subsystem with bytes reversed.
>=20
> Does the kernel have any dedicated function for just always swapping?
>=20

After some more thought on the train home:

I think the correct construct would be cpu_to_le32(be32_to_cpu(data[i]))
This would correctly reflect that the data is read from big-endian
memory and subsequently written to little-endian "memory" (aka the EIP).
It also fits in nicely with your other changes. Could you work that into
a patch v2? Then I would ack it (after testing).

> Anyway: NACK on this patch for now due to this.
>=20
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> > drivers/crypto/inside-secure/safexcel.c:306:17: warning: cast to restri=
cted __be32
> >
> > Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > ---
> > Cc: Antoine Tenart <antoine.tenart@bootlin.com>
> > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Cc: linux-crypto@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > ---
> >  drivers/crypto/inside-secure/safexcel.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/crypto/inside-secure/safexcel.c b/drivers/crypto/i=
nside-
> secure/safexcel.c
> > index 223d1bfdc7e6..dd33f6dda295 100644
> > --- a/drivers/crypto/inside-secure/safexcel.c
> > +++ b/drivers/crypto/inside-secure/safexcel.c
> > @@ -298,13 +298,13 @@ static void eip197_init_firmware(struct safexcel_=
crypto_priv
> *priv)
> >  static int eip197_write_firmware(struct safexcel_crypto_priv *priv,
> >  				  const struct firmware *fw)
> >  {
> > -	const u32 *data =3D (const u32 *)fw->data;
> > +	const __be32 *data =3D (const __be32 *)fw->data;
> >  	int i;
> >
> >  	/* Write the firmware */
> > -	for (i =3D 0; i < fw->size / sizeof(u32); i++)
> > +	for (i =3D 0; i < fw->size / sizeof(__be32); i++)
> >  		writel(be32_to_cpu(data[i]),
> > -		       priv->base + EIP197_CLASSIFICATION_RAMS + i * sizeof(u32));
> > +		       priv->base + EIP197_CLASSIFICATION_RAMS + i * sizeof(__be32))=
;
> >
> >  	/* Exclude final 2 NOPs from size */
> >  	return i - EIP197_FW_TERMINAL_NOPS;
> > --
> > 2.23.0
>=20
> Regards,
> Pascal van Leeuwen
> Silicon IP Architect, Multi-Protocol Engines @ Verimatrix
> www.insidesecure.com

Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Verimatrix
www.insidesecure.com