On Sun, Dec 08, 2019 at 01:42:29PM +0800, Herbert Xu wrote: > As it stands we only enforce descsize limits when an algorithm is > registered. However, as descsize is dynamic and may be set at > init_tfm time this is not enough. This is why hmac has its own > descsize check. > > This series adds descsize limit enforcement at init_tfm time so > that the API takes over the responsibility of checking descsize > after the algorithm's init_tfm has completed. > > v2 addresses the issues raised during review, including adding > a WARN_ON_ONCE to crypto_shash_init_tfm. > > Thanks, I left some nits on patches 1 and 2, but not too important. Feel free to add: Reviewed-by: Eric Biggers <ebiggers@xxxxxxxxxx>
