From: Willy Tarreau <w@1wt.eu>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH stable 3.10.y 00/18] Backport crypto fixes.
Date: Thu, 27 Oct 2016 17:06:14 +0200 [thread overview]
Message-ID: <20161027150614.GB12104@1wt.eu> (raw)
In-Reply-To: <1477578591-28924-1-git-send-email-aryabinin@virtuozzo.com>
Hi Andrey,
On Thu, Oct 27, 2016 at 05:29:33PM +0300, Andrey Ryabinin wrote:
> While fuzzing our 3.10 based kernel we observed some crashes, e.g:
> http://lkml.kernel.org/r/<CACT4Y+aE-pNUnCLbDQkFQ9Y7QivN_g6hEuS7t1RpknPHFmHg+g@mail.gmail.com>
>
> It appears that 3.10-stable lacks some crypto related fixes. Here is my attempt
> to backport them.
> Many patches didn't apply cleanly, so to make sure that my conflict resolution
> is correct I compared it with other stable trees.
(...)
Thanks a lot for doing this! I'm queueing them for next 3.10 and will merge
them unless I receive a nack for any of them.
Best regards,
Willy
prev parent reply other threads:[~2016-10-27 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 14:29 [PATCH stable 3.10.y 00/18] Backport crypto fixes Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 01/18] crypto: algif_skcipher - Require setkey before accept(2) Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 02/18] crypto: af_alg - Disallow bind/setkey/... after accept(2) Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 03/18] crypto: af_alg - Add nokey compatibility path Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 04/18] crypto: algif_skcipher " Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 05/18] crypto: hash - Add crypto_ahash_has_setkey Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 06/18] crypto: algif_hash - Require setkey before accept(2) Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 07/18] crypto: skcipher - Add crypto_skcipher_has_setkey Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 08/18] crypto: algif_skcipher - Add key check exception for cipher_null Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 09/18] crypto: af_alg - Allow af_af_alg_release_parent to be called on nokey path Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 10/18] crypto: algif_hash - Remove custom release parent function Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 11/18] crypto: algif_skcipher " Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 12/18] crypto: af_alg - Forbid bind(2) when nokey child sockets are present Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 13/18] crypto: algif_hash - Fix race condition in hash_check_key Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 14/18] crypto: algif_skcipher - Fix race condition in skcipher_check_key Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 15/18] crypto: algif_skcipher - Load TX SG list after waiting Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 16/18] crypto: shash - Fix has_key setting Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 17/18] crypto: cryptd - initialize child shash_desc on import Andrey Ryabinin
2016-10-27 14:29 ` [PATCH stable 3.10.y 18/18] crypto: skcipher - Fix blkcipher walk OOM crash Andrey Ryabinin
2016-10-27 15:06 ` Willy Tarreau [this message]
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=20161027150614.GB12104@1wt.eu \
--to=w@1wt.eu \
--cc=aryabinin@virtuozzo.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).