[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <VI1PR04MB444593F54DFB2EDC0016F56E8CCB0@VI1PR04MB4445.eurprd04.prod.outlook.com>
Date: Fri, 19 Jul 2019 07:13:58 +0000
From: Iuliana Prodan <iuliana.prodan@....com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: "David S. Miller" <davem@...emloft.net>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH] crypto: gcm - restrict assoclen for rfc4543
On 7/18/2019 6:11 PM, Herbert Xu wrote:
> On Thu, Jul 18, 2019 at 10:59:07PM +0800, Herbert Xu wrote:
>>
>> So I presume the driver does enforce the limit. Please actually
>> state that in the commit description for future reference.
>
> Also have you looked at whether other drivers would be affected
> by this? It wouldn't be so nice if this change makes other drivers
> fail the same test as a result.
I've checked the other drivers and I found rfc4543 support in bcm and
ccree. I've sent fixes for these two, but I don't have hardware to test
on, so they are just compile tested.
Link: https://patchwork.kernel.org/project/linux-crypto/list/?series=147747
Regards,
Iulia
Powered by blists - more mailing lists