Re: general protection fault in __crypto_alg_lookup

On Tue, Dec 19, 2017 at 11:49:02PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 6084b576dca2e898f5c101baef151f7bfdbb606d > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: BUG: unable to handle kernel NULL pointer dereference in crypto_alg_tested

On Fri, Dec 22, 2017 at 11:33:02PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 6084b576dca2e898f5c101baef151f7bfdbb606d > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: general protection fault in crypto_remove_spawns

On Mon, Nov 27, 2017 at 10:56:46AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 1ea8d039f9edcfefb20d8ddfe136930f6e551529 > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > C

Re: KASAN: slab-out-of-bounds Write in sha3_update (2)

On Fri, Dec 22, 2017 at 11:22:38AM -0600, Eric Biggers wrote: > [+Cc keyri...@vger.kernel.org] > > On Fri, Dec 22, 2017 at 07:55:01AM -0800, syzbot wrote: > > Hello, > > > > syzkaller hit the following crash on > > 9035a8961b504d0997369509ab8c6b1f0a4ee33d > >

Re: kernel failure while loading X.509 certificate

> Il giorno 17 gen 2018, alle ore 06:44, Eric Biggers ha > scritto: > > On Wed, Jan 17, 2018 at 06:36:16AM +0100, Paolo Valente wrote: >> >> >>> Il giorno 17 gen 2018, alle ore 06:16, Eric Biggers >>> ha scritto: >>> >>> Hi Paolo, >>> >>> On

Re: kernel failure while loading X.509 certificate

On Wed, Jan 17, 2018 at 06:36:16AM +0100, Paolo Valente wrote: > > > > Il giorno 17 gen 2018, alle ore 06:16, Eric Biggers > > ha scritto: > > > > Hi Paolo, > > > > On Fri, Jan 12, 2018 at 07:06:12AM +0100, Paolo Valente wrote: > >> > >> > >>> Il giorno 11 gen 2018,

Re: kernel failure while loading X.509 certificate

> Il giorno 17 gen 2018, alle ore 06:16, Eric Biggers ha > scritto: > > Hi Paolo, > > On Fri, Jan 12, 2018 at 07:06:12AM +0100, Paolo Valente wrote: >> >> >>> Il giorno 11 gen 2018, alle ore 23:37, Arnd Bergmann ha >>> scritto: >>> >>> On Thu, Jan 11,

Re: kernel failure while loading X.509 certificate

Hi Paolo, On Fri, Jan 12, 2018 at 07:06:12AM +0100, Paolo Valente wrote: > > > > Il giorno 11 gen 2018, alle ore 23:37, Arnd Bergmann ha > > scritto: > > > > On Thu, Jan 11, 2018 at 7:29 PM, Paolo Valente > > wrote: > >> Hi guys, > >> this is a help

Re: [RFT PATCH] crypto: arm64 - implement SM3 secure hash using special instructions

On Tue, Jan 16, 2018 at 08:29:22AM +, Ard Biesheuvel wrote: > Implement the Chinese SM3 secure hash algorithm using the new > special instructions that have been introduced as an optional > extension in ARMv8.2. > Hi Ard, I've tested this in a model against 4.15-rc8. The following tcrypt

AES-NI: BUG in gcmaes_decrypt

Hi, When compiling the current cryptodev-2.6 tree with CONFIG_DEBUG_SG and invoking a gcm(aes) decrypt operation with an empty ciphertext and an empty AAD, I get the following BUG: [ 79.294243] [ cut here ] [ 79.294903] kernel BUG at

[PATCH v2] crypto/ahash: Require export/import in ahash

Export and import were optional in async hash. As most drivers were rewritten, they become mandatory now, so correct init of ahash transformation. Signed-off-by: Kamil Konieczny --- This is resend of previous patch. As Bartlomiej Zolnierkiewicz pointed out, there

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

On 16.01.2018 18:28, Fabio Estevam wrote: > Hi Kamil, > > On Tue, Jan 16, 2018 at 2:16 PM, Kamil Konieczny > wrote: >> Crypto framework will require async hash export/import, so add empty >> functions to prevent OOPS. > > Which Oops exactly are you getting?

Re: [PATCH v2] net/core: Increase default optmem_max limit

Am Dienstag, 16. Januar 2018, 18:16:43 CET schrieb Björn 'besser82' Esser: Hi Björn, > With the new Linux Kernel Crypto API User Space Interface > and its underlying AF_ALG socket, the current default value > for `net.core.optmem_max` can be exhausted pretty quick when > using asynchronous IO;

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

On 16.01.2018 17:56, Marek Vasut wrote: > On 01/16/2018 05:16 PM, Kamil Konieczny wrote: >> Crypto framework will require async hash export/import, so add empty >> functions to prevent OOPS. > > Shouldn't this be handled on the subsystem level with some > > if (foo->bar) > foo->bar(); > >

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

Hi Kamil, On Tue, Jan 16, 2018 at 2:16 PM, Kamil Konieczny wrote: > Crypto framework will require async hash export/import, so add empty > functions to prevent OOPS. Which Oops exactly are you getting? Just booted 4.14.13 and the mxs-dcp driver does not even

Re: [PATCH v2] net/core: Increase default optmem_max limit

With the new Linux Kernel Crypto API User Space Interface and its underlying AF_ALG socket, the current default value for `net.core.optmem_max` can be exhausted pretty quick when using asynchronous IO; on 32 bit systems it is not even enough for sending about 10 IOVECs at once to the socket

[PATCH v2] net/core: Increase default optmem_max limit

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

On 01/16/2018 05:16 PM, Kamil Konieczny wrote: > Crypto framework will require async hash export/import, so add empty > functions to prevent OOPS. Shouldn't this be handled on the subsystem level with some if (foo->bar) foo->bar(); instead? > Signed-off-by: Kamil Konieczny

[PATCH] crypto: ux500/hash: Add empty export and import

Crypto framework will require async hash export/import, so add empty functions to prevent OOPS. Signed-off-by: Kamil Konieczny --- drivers/crypto/ux500/hash/hash_core.c | 18 ++ 1 file changed, 18 insertions(+) diff --git

[PATCH] crypto: n2_core: Add empty hash export and import

Crypto framework will require async hash export/import, so add empty functions to prevent OOPS. Signed-off-by: Kamil Konieczny --- drivers/crypto/n2_core.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/crypto/n2_core.c

[PATCH] crypto: mxs-dcp: Add empty hash export and import

Crypto framework will require async hash export/import, so add empty functions to prevent OOPS. Signed-off-by: Kamil Konieczny --- drivers/crypto/mxs-dcp.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/drivers/crypto/mxs-dcp.c

[PATCH] crypto: testmgr.c: test misuse of result in ahash

Async hash operations can use result pointer in final/finup/digest, but not in init/update/export/import, so test it for misuse. Signed-off-by: Kamil Konieczny --- Tested with crypto run-time self test on Odroid-U3 with Exynos 4412 CPU with insmod s5p-sss.ko

Re: [RFT PATCH] crypto: ahash.c: Require export/import in ahash

On Tuesday, January 16, 2018 11:35:44 AM Kamil Konieczny wrote: > Export and import were optional in async hash. As drivers were rewritten, > they become mandatory now, so correct init of ahash transformation. > > Signed-off-by: Kamil Konieczny > --- > Tested

[bug report] crypto: ccp: Add Secure Encrypted Virtualization (SEV) command support

Hello Brijesh Singh, The patch 200664d5237f: "crypto: ccp: Add Secure Encrypted Virtualization (SEV) command support" from Dec 4, 2017, leads to the following static checker warning: drivers/crypto/ccp/psp-dev.c:779 psp_pci_init() error: uninitialized symbol 'error'.

Re: [RFC] AF_ALG AIO and IV

On Tue, 16 Jan 2018 07:28:06 +0100 Stephan Mueller wrote: > Am Montag, 15. Januar 2018, 15:42:58 CET schrieb Jonathan Cameron: > > Hi Jonathan, > > > > What about: > > > > > > sendmsg(IV, data) > > > sendmsg(data) > > > .. > > > AIO recvmsg with multiple IOCBs > > > AIO

[RFT PATCH] crypto: ahash.c: Require export/import in ahash

Export and import were optional in async hash. As drivers were rewritten, they become mandatory now, so correct init of ahash transformation. Signed-off-by: Kamil Konieczny --- Tested with crypto run-time self test on Odroid-U3 with Exynos 4412 CPU, with insmod

TRADING ACCOUNT

Hi , I MONIRA François managing director of THALES COMMUNICATIONS & SECURITY S.A.S .I send you this email after visiting your website , regarding the possibility to open a trading account with your company . We are a company based in France specialised in supplying Multi -media, wholesaler

Re: [PATCH 0/5] sha3 fixes and new implementation for arm64

On 16 January 2018 at 08:41, Steve Capper wrote: > On Fri, Jan 12, 2018 at 03:13:56PM +, Ard Biesheuvel wrote: >> On 12 January 2018 at 13:15, Ard Biesheuvel >> wrote: >> > Add an implementation of SHA3 to arm64 using the new special

Re: [PATCH 0/5] sha3 fixes and new implementation for arm64

On Fri, Jan 12, 2018 at 03:13:56PM +, Ard Biesheuvel wrote: > On 12 January 2018 at 13:15, Ard Biesheuvel wrote: > > Add an implementation of SHA3 to arm64 using the new special instructions > > (#4) > > > > In preparation of that, fix a bug in the SHA3 and

[RFT PATCH] crypto: arm64 - implement SM3 secure hash using special instructions

Implement the Chinese SM3 secure hash algorithm using the new special instructions that have been introduced as an optional extension in ARMv8.2. Signed-off-by: Ard Biesheuvel --- arch/arm64/crypto/Kconfig | 5 ++ arch/arm64/crypto/Makefile | 3 +

Re: [RFT PATCH] crypto: arm64 - implement SHA-512 using special instructions

On 16 January 2018 at 08:16, Steve Capper wrote: > On Tue, Jan 09, 2018 at 06:23:02PM +, Ard Biesheuvel wrote: >> Implement the SHA-512 using the new special instructions that have >> been introduced as an optional extension in ARMv8.2. > > Hi Ard, > I have tested this

Re: [RFT PATCH] crypto: arm64 - implement SHA-512 using special instructions

On Tue, Jan 09, 2018 at 06:23:02PM +, Ard Biesheuvel wrote: > Implement the SHA-512 using the new special instructions that have > been introduced as an optional extension in ARMv8.2. Hi Ard, I have tested this applied on top of 4.15-rc7 running in a model. For sha512-ce, I verified that