Sorry for replying to old mail...
On Wed, Jun 14, 2017 at 11:37:39AM -0700, Dave Watson wrote:
> +static int tls_do_encryption(struct tls_context *tls_ctx,
> + struct tls_sw_context *ctx, size_t data_len,
> + gfp_t flags)
> +{
> + unsigned int
kill_fq removes a complete frame queue, it needs to free the qman_fq
in the last. Else kmemleak will report the below warning:
unreferenced object 0x800073085c80 (size 128):
comm "cryptomgr_test", pid 199, jiffies 4294937850 (age 67.840s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00
On Mon, Jul 10, 2017 at 11:51:42AM -0700, Linus Torvalds wrote:
> Heh, I already did this in commit b4b8cbf679c4.
>
> I complained because I want maintainers to be aware of this issue -
> adding Kconfig options with defaults that don't make sense should be
> caught earlier than when I do a test bu
Heh, I already did this in commit b4b8cbf679c4.
I complained because I want maintainers to be aware of this issue -
adding Kconfig options with defaults that don't make sense should be
caught earlier than when I do a test built..
Linus
On Mon, Jul 10, 2017 at 3:15 AM, Herbert X
On Mon, Jul 10, 2017 at 08:10:02AM -0400, Sowmini Varadhan wrote:
>
> The reason that the WARN_ON is triggered is that af_alg_accept() calls
> sock_init_data() which does
>
>2636 if (sock) {
> :
>2639 sock->sk= sk;
Oh yes. This started out with
There are quite a number of occurrences in the kernel of the pattern
if (dst != src)
memcpy(dst, src, walk.total % AES_BLOCK_SIZE);
crypto_xor(dst, final, walk.total % AES_BLOCK_SIZE);
or
crypto_xor(keystream, src, nbytes);
memcpy(dst, keystream, nbytes);
where crypt
>From 2/2:
"""
There are quite a number of occurrences in the kernel of the pattern
if (dst != src)
memcpy(dst, src, walk.total % AES_BLOCK_SIZE);
crypto_xor(dst, final, walk.total % AES_BLOCK_SIZE);
or
crypto_xor(keystream, src, nbytes);
memcpy(dst, keystream, nbyte
In preparation of updating crypto_xor() [which is what the crypto API
exposes to other subsystems] to use separate operands for input and
output, first modify the __crypto_xor() implementation that provides
the actual functionality when not using the inline version.
Signed-off-by: Ard Biesheuvel
Drivers should not enable themselves by default, unless they're
an integral part of the platform.
Reported-by: Linus Torvalds
Signed-off-by: Herbert Xu
diff --git a/drivers/crypto/cavium/nitrox/Kconfig
b/drivers/crypto/cavium/nitrox/Kconfig
index 731e6a5..181a1df 100644
--- a/drivers/crypto/ca
