On 24/06/16 13:32, Herbert Xu wrote:
On Wed, Jun 22, 2016 at 04:23:39PM +0300, Tero Kristo wrote:
The statesize is used to determine the maximum size for saved ahash
context. In some cases, this can be much larger than what is currently
allocated for it, for example omap-sham driver uses a buffer size of
PAGE_SIZE. Increase the statesize to accommodate this.
Signed-off-by: Tero Kristo <t-kristo@xxxxxx>
Nack. The exported state is supposed to consist of the actual
hash state, plus at most one block worth of unhashed data. It's
limited so that we can store it on the stack.
So no I'm not taking this patch.
Ok, I think I need to allocate the storage space locally then within the
driver. Would it be ok to call kmalloc / free in the export / import
implementation of the driver? The size of the unhashed buffer in
omap-sham is unfortunately rather large.
-Tero
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
