Re: general protection fault in crypto_remove_spawns

From: Stephan Müller
Date: Tue Nov 28 2017 - 17:06:26 EST


Am Montag, 27. November 2017, 19:56:46 CET schrieb syzbot:

Hi Herbert,

The issue seems to trigger a bug whose results we have seen before. When
starting the reproducer and stopping it shortly thereafter, I see the numerous
identical entries in /proc/crypto:

name : cmac(des3_ede)
driver : cmac(des3_ede-asm)
module : kernel
priority : 200
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 8
digestsize : 8

name : cmac(des3_ede)
driver : cmac(des3_ede-asm)
module : kernel
priority : 200
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 8
digestsize : 8

name : cmac(des3_ede)
driver : cmac(des3_ede-asm)
module : kernel
priority : 200
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 8
digestsize : 8

...

And this list keeps on growing without end:

# ./repro

# less /proc/crypto | wc
9559 26456 188754

# ./repro

# less /proc/crypto | wc
11440 31586 226032

At one point in time I think the system simply has too many entries.

Ciao
Stephan