On Fri, Dec 23, 2022 at 06:47:19PM +0100, Uwe Kleine-König wrote: > > Using > > if (data && len) > > fixes it (that's the patch that b4 picks for the above message id :-\), > > if (!IS_ENABLED(CONFIG_CRYPTO_DEV_FSL_CAAM_DEBUG) && len) > > makes the problem go away, too. But I wonder if the latter is correct. Thanks for confirming! > Shouldn't the memcpy happen even with that debugging symbol enabled? It's just a pecularity with gcc. It only produces the warning because of the extra complexities introduced by the debugging code. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
