From: Kees Cook <keescook@chromium.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Eric Biggers <ebiggers@google.com>,
Alasdair Kergon <agk@redhat.com>,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
Lars Persson <larper@axis.com>, Mike Snitzer <snitzer@redhat.com>,
Rabin Vincent <rabinv@axis.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
qat-linux@intel.com, dm-devel@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 11/14] treewide: Prepare to remove VLA usage for AHASH_REQUEST_ON_STACK
Date: Wed, 18 Jul 2018 20:09:01 -0700 [thread overview]
Message-ID: <CAGXu5jJyyi1FvT9PytMkU_rPeSqMSHR7asjn8ykShZGGRPPRDg@mail.gmail.com> (raw)
In-Reply-To: <B278D0F7-71B6-4F3D-B625-D8B0298CE5B4@linaro.org>
On Wed, Jul 18, 2018 at 7:55 PM, Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> I have only build tested it, so if you make sure that it does not break anything, please go ahead.
I can give it a spin; what's the best way? Is CONFIG_CRYPTO_MANAGER=y
sufficient?
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2018-07-19 3:09 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 20:36 [PATCH v4 00/14] crypto: Remove VLA usage Kees Cook
2018-07-11 20:36 ` [PATCH v4 01/14] crypto: xcbc: " Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 02/14] crypto: cbc: " Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 03/14] crypto: shash: " Kees Cook
2018-07-11 20:36 ` [PATCH v4 04/14] dm integrity: " Kees Cook
2018-07-11 20:36 ` [PATCH v4 05/14] crypto: ahash: " Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 06/14] dm verity fec: " Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 07/14] crypto alg: Introduce generic max blocksize and alignmask Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 08/14] crypto: qat: Remove VLA usage Kees Cook
2018-07-11 20:36 ` [PATCH v4 09/14] crypto: shash: Remove VLA usage in unaligned hashing Kees Cook
2018-07-11 20:36 ` [PATCH v4 10/14] kbuild: Introduce FRAME_WARN_BUMP_FLAG Kees Cook
2018-07-11 20:36 ` Kees Cook
2018-07-11 20:36 ` [PATCH v4 11/14] treewide: Prepare to remove VLA usage for AHASH_REQUEST_ON_STACK Kees Cook
2018-07-12 16:02 ` Arnd Bergmann
2018-07-12 16:02 ` Arnd Bergmann
2018-07-12 20:17 ` Kees Cook
2018-07-12 20:17 ` Kees Cook
2018-07-12 21:38 ` Arnd Bergmann
2018-07-12 21:38 ` Arnd Bergmann
2018-07-13 0:40 ` Herbert Xu
2018-07-13 0:40 ` Herbert Xu
2018-07-13 3:33 ` Kees Cook
2018-07-13 3:33 ` Kees Cook
2018-07-13 3:44 ` Herbert Xu
2018-07-13 3:44 ` Herbert Xu
2018-07-13 5:17 ` Kees Cook
2018-07-13 5:17 ` Kees Cook
2018-07-13 5:20 ` Herbert Xu
2018-07-13 5:20 ` Herbert Xu
2018-07-13 6:00 ` Kees Cook
2018-07-13 6:00 ` Kees Cook
2018-07-13 10:14 ` Arnd Bergmann
2018-07-13 10:14 ` Arnd Bergmann
2018-07-15 4:28 ` Kees Cook
2018-07-15 4:28 ` Kees Cook
2018-07-17 20:59 ` Arnd Bergmann
2018-07-17 20:59 ` Arnd Bergmann
2018-07-18 14:50 ` Ard Biesheuvel
2018-07-18 14:50 ` Ard Biesheuvel
2018-07-18 15:19 ` Ard Biesheuvel
2018-07-18 15:19 ` Ard Biesheuvel
2018-07-18 15:33 ` Arnd Bergmann
2018-07-18 15:33 ` Arnd Bergmann
2018-07-18 15:33 ` Ard Biesheuvel
2018-07-18 15:33 ` Ard Biesheuvel
2018-07-19 2:51 ` Kees Cook
2018-07-19 2:51 ` Kees Cook
2018-07-19 2:55 ` Ard Biesheuvel
2018-07-19 2:55 ` Ard Biesheuvel
2018-07-19 3:09 ` Kees Cook [this message]
2018-07-19 3:09 ` Kees Cook
2018-07-19 3:13 ` Ard Biesheuvel
2018-07-19 3:13 ` Ard Biesheuvel
2018-07-19 14:54 ` Ard Biesheuvel
2018-07-19 14:54 ` Ard Biesheuvel
2018-07-19 18:44 ` Kees Cook
2018-07-19 18:44 ` Kees Cook
2018-07-13 6:16 ` Kees Cook
2018-07-13 6:16 ` Kees Cook
2018-07-13 6:22 ` Herbert Xu
2018-07-13 6:22 ` Herbert Xu
2018-07-14 3:07 ` Kees Cook
2018-07-14 3:07 ` Kees Cook
2018-07-15 2:44 ` Herbert Xu
2018-07-15 2:44 ` Herbert Xu
2018-07-15 2:59 ` Kees Cook
2018-07-15 2:59 ` Kees Cook
2018-07-16 0:01 ` Herbert Xu
2018-07-16 0:01 ` Herbert Xu
2018-07-16 3:39 ` Kees Cook
2018-07-16 3:39 ` Kees Cook
2018-07-16 7:24 ` Arnd Bergmann
2018-07-16 7:24 ` Arnd Bergmann
2018-07-11 20:36 ` [PATCH v4 12/14] crypto: ahash: Remove " Kees Cook
2018-07-11 20:36 ` [PATCH v4 13/14] rxrpc: Prepare to remove VLA usage for SKCIPHER_REQUEST_ON_STACK Kees Cook
2018-07-12 15:11 ` Arnd Bergmann
2018-07-12 15:11 ` Arnd Bergmann
2018-07-12 15:11 ` Arnd Bergmann
2018-07-12 20:23 ` Kees Cook
2018-07-12 20:23 ` Kees Cook
2018-07-12 20:30 ` Kees Cook
2018-07-12 20:30 ` Kees Cook
2018-07-12 21:15 ` Arnd Bergmann
2018-07-12 21:15 ` Arnd Bergmann
2018-07-12 21:38 ` Kees Cook
2018-07-12 21:38 ` Kees Cook
2018-07-12 21:28 ` David Howells
2018-07-12 21:28 ` David Howells
2018-07-12 21:34 ` Kees Cook
2018-07-12 21:34 ` Kees Cook
2018-07-12 22:05 ` David Howells
2018-07-12 22:05 ` David Howells
2018-07-11 20:36 ` [PATCH v4 14/14] crypto: skcipher: Remove " Kees Cook
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=CAGXu5jJyyi1FvT9PytMkU_rPeSqMSHR7asjn8ykShZGGRPPRDg@mail.gmail.com \
--to=keescook@chromium.org \
--cc=agk@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=giovanni.cabiddu@intel.com \
--cc=gustavo@embeddedor.com \
--cc=herbert@gondor.apana.org.au \
--cc=larper@axis.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=rabinv@axis.com \
--cc=snitzer@redhat.com \
--cc=tim.c.chen@linux.intel.com \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.