From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Harsh Jain <harshjain.prof@gmail.com>, linux-crypto@vger.kernel.org
Subject: Re: crypto: algif_hash - Only export and import on sockets with data
Date: Sat, 31 Oct 2015 00:45:47 +0100 [thread overview]
Message-ID: <2587504.xtsMOV5mei@myon.chronox.de> (raw)
In-Reply-To: <20151030121651.GA23757@gondor.apana.org.au>
Am Freitag, 30. Oktober 2015, 20:16:51 schrieb Herbert Xu:
Hi Herbert,
>
> setkey should be needed as the subsequent accept will all be based
> on the same parent fd, meaning that they will all use a single tfm.
>
> Please try the following patch.
Testing complete: patch solves the oops and allows to successfully perform
HMAC even when having subsequent accepts and operating on those subsequent
accepts.
--
Ciao
Stephan
next prev parent reply other threads:[~2015-10-30 23:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 6:26 kernel tainted while exporting shash context using af_alg interface Harsh Jain
2015-10-25 11:58 ` Stephan Mueller
2015-10-26 6:19 ` Harsh Jain
2015-10-26 9:21 ` Harsh Jain
2015-10-28 0:09 ` Stephan Mueller
2015-10-28 0:55 ` Stephan Mueller
2015-10-28 10:54 ` Harsh Jain
2015-10-28 11:23 ` Stephan Mueller
2015-10-30 8:32 ` Harsh Jain
2015-10-30 11:10 ` Stephan Mueller
2015-10-30 12:16 ` crypto: algif_hash - Only export and import on sockets with data Herbert Xu
2015-10-30 23:45 ` Stephan Mueller [this message]
2015-11-01 9:11 ` [PATCH v2] " Herbert Xu
2015-11-01 11:06 ` Stephan Mueller
2015-11-01 11:07 ` Stephan Mueller
2015-11-02 3:12 ` Herbert Xu
2015-11-05 7:42 ` Harsh Jain
2015-11-05 12:19 ` Herbert Xu
2015-11-02 5:48 ` kernel tainted while exporting shash context using af_alg interface Harsh Jain
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=2587504.xtsMOV5mei@myon.chronox.de \
--to=smueller@chronox.de \
--cc=harshjain.prof@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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