From: "Stephan Müller" <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: syzbot
<bot+b6e703f648ebbbf57a4528d4314e0c2a5c893dc2@syzkaller.appspotmail.com>,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in crypto_remove_spawns
Date: Tue, 28 Nov 2017 23:06:18 +0100 [thread overview]
Message-ID: <2621541.YkCu9MsXr4@positron.chronox.de> (raw)
In-Reply-To: <001a1141c43ad30ccf055efb76ed@google.com>
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
next prev parent reply other threads:[~2017-11-28 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 18:56 syzbot
2017-11-28 22:06 ` Stephan Müller [this message]
2017-12-12 6:09 ` [PATCH] crypto: AF_ALG - limit mask and type Stephan Müller
2017-12-12 8:57 ` Eric Biggers
2017-12-12 9:22 ` Stephan Mueller
2017-12-19 6:25 ` [PATCH v2] " Stephan Müller
2017-12-22 7:36 ` Herbert Xu
2017-12-22 7:41 ` Stephan Mueller
2017-12-22 7:58 ` Herbert Xu
2018-01-02 7:53 ` [PATCH v3] crypto: AF_ALG - whitelist " Stephan Müller
2018-01-02 7:55 ` [PATCH v4] " Stephan Müller
2018-01-12 12:23 ` Herbert Xu
2017-12-29 20:30 ` [PATCH] crypto: algapi - fix NULL dereference in crypto_remove_spawns() Eric Biggers
2018-01-05 11:18 ` Herbert Xu
2018-01-17 6:34 ` general protection fault in crypto_remove_spawns Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2621541.YkCu9MsXr4@positron.chronox.de \
--to=smueller@chronox.de \
--cc=bot+b6e703f648ebbbf57a4528d4314e0c2a5c893dc2@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®