Re: drivers/crypto/chelsio/chcr_ktls.c:1078: undefined reference to `tls_get_record'

On 8/7/20 9:16 AM, kernel test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 86cfccb66937dd6cbf26ed619958b9e587e6a115 commit: 5a4b9fe7fece62ecab6fb28fe92362f83b41c33e cxgb4/chcr: complete record tx handling date: 5 months ago config: pa

Re: [PATCH] module: statically initialize init section freeing data

On Thu, Oct 08, 2020 at 01:32:20PM -0400, Daniel Jordan wrote: > Corentin hit the following workqueue warning when running with > CRYPTO_MANAGER_EXTRA_TESTS: > > WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 > Modules linked in: ghash_generic > CPU: 2 PID: 147

Re: [v2 PATCH] crypto: sun4i-ss - Fix sparse endianness markers

On Thu, Oct 08, 2020 at 08:36:23AM +0200, Corentin Labbe wrote: > On Thu, Oct 08, 2020 at 04:52:38PM +1100, Herbert Xu wrote: > > On Thu, Sep 24, 2020 at 03:27:38PM +0200, Corentin Labbe wrote: > > > > > > This is an example on next-20200923+BigEndian > > > alg: ahash: sha1 test failed (wrong resul

Re: [PATCH] random: use correct memory barriers for crng_node_pool

On Thu, Oct 01, 2020 at 08:07:31PM -0700, Eric Biggers wrote: > On Thu, Sep 24, 2020 at 08:31:02PM -0700, Paul E. McKenney wrote: > > On Thu, Sep 24, 2020 at 07:09:08PM -0700, Eric Biggers wrote: > > > On Thu, Sep 24, 2020 at 05:59:34PM -0700, Paul E. McKenney wrote: > > > > On Tue, Sep 22, 2020 at

[PATCH] module: statically initialize init section freeing data

Corentin hit the following workqueue warning when running with CRYPTO_MANAGER_EXTRA_TESTS: WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 Modules linked in: ghash_generic CPU: 2 PID: 147 Comm: modprobe Not tainted 5.6.0-rc1-next-20200214-00068-g166c9264f0b

Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0

On Wed, Oct 07, 2020 at 09:41:17PM +0200, Corentin Labbe wrote: > I have added CONFIG_FTRACE=y and your second patch. > The boot log can be seen at http://kernel.montjoie.ovh/108789.log > > But it seems the latest dump_stack addition flood a bit. Heh, sorry for making it spew, there wasn't such a

Re: [PATCH] crypto: talitos - Fix sparse warnings

Le 07/10/2020 à 08:50, Herbert Xu a écrit : On Sat, Oct 03, 2020 at 07:15:53PM +0200, Christophe Leroy wrote: The following changes fix the sparse warnings with less churn: Yes that works too. Can you please submit this patch? This fixed two independant commits from the past. I sent ou

[PATCH] crypto: talitos - Fix return type of current_desc_hdr()

current_desc_hdr() returns a u32 but in fact this is a __be32, leading to a lot of sparse warnings. Change the return type to __be32 and ensure it is handled as sure by the caller. Fixes: 3e721aeb3df3 ("crypto: talitos - handle descriptor not found in error path") Signed-off-by: Christophe Leroy

[PATCH] crypto: talitos - Endianess in current_desc_hdr()

current_desc_hdr() compares the value of the current descriptor with the next_desc member of the talitos_desc struct. While the current descriptor is obtained from in_be32() which return CPU ordered bytes, next_desc member is in big endian order. Convert the current descriptor into big endian bef