From: Salvatore Mesoraca <s.mesoraca16@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-hardening@lists.openwall.com,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kees Cook <keescook@chromium.org>,
Salvatore Mesoraca <s.mesoraca16@gmail.com>,
Eric Biggers <ebiggers3@gmail.com>,
Laura Abbott <labbott@redhat.com>
Subject: [PATCH 0/6] Remove several VLAs in the crypto subsystem
Date: Sat, 7 Apr 2018 20:38:17 +0200 [thread overview]
Message-ID: <1523126303-23205-1-git-send-email-s.mesoraca16@gmail.com> (raw)
As suggested by Laura Abbott[2], I'm resending my patch with
MAX_BLOCKSIZE and MAX_ALIGNMASK defined in an header, so they
can be used in other places.
I take this opportuinuty to deal with some other VLAs not
handled in the old patch.
[1] http://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qPXydAacU1RqZWA@mail.gmail.com
[2] http://lkml.kernel.org/r/4e536889-439a-49e6-dd95-2d4286913202@redhat.com
Salvatore Mesoraca (6):
crypto: api - laying macros for statically allocated buffers
crypto: ctr - avoid VLA use
crypto: api - avoid VLA use
crypto: pcbc - avoid VLA use
crypto: cts - avoid VLA use
crypto: cfb - avoid VLA use
crypto/cfb.c | 14 ++++++++++----
crypto/cipher.c | 7 ++++++-
crypto/ctr.c | 13 +++++++++++--
crypto/cts.c | 8 ++++++--
crypto/internal.h | 8 ++++++++
crypto/pcbc.c | 9 +++++++--
6 files changed, 48 insertions(+), 11 deletions(-)
--
1.9.1
next reply other threads:[~2018-04-07 18:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 18:38 Salvatore Mesoraca [this message]
2018-04-07 18:38 ` [PATCH 1/6] crypto: api - laying macros for statically allocated buffers Salvatore Mesoraca
2018-04-08 3:15 ` Herbert Xu
2018-04-08 8:56 ` Salvatore Mesoraca
2018-04-07 18:38 ` [PATCH 2/6] crypto: ctr - avoid VLA use Salvatore Mesoraca
2018-04-08 3:19 ` Herbert Xu
2018-04-08 8:58 ` Salvatore Mesoraca
2018-04-08 9:18 ` Herbert Xu
2018-04-07 18:38 ` [PATCH 3/6] crypto: api " Salvatore Mesoraca
2018-04-08 3:16 ` Herbert Xu
2018-04-08 9:07 ` Salvatore Mesoraca
2018-04-08 9:22 ` Herbert Xu
2018-04-09 13:27 ` Salvatore Mesoraca
2018-04-07 18:38 ` [PATCH 4/6] crypto: pcbc " Salvatore Mesoraca
2018-04-07 18:38 ` [PATCH 5/6] crypto: cts " Salvatore Mesoraca
2018-04-07 18:38 ` [PATCH 6/6] crypto: cfb " Salvatore Mesoraca
2018-04-07 19:56 ` [PATCH 0/6] Remove several VLAs in the crypto subsystem Kees Cook
2018-04-08 8:55 ` Salvatore Mesoraca
2018-04-09 13:53 Salvatore Mesoraca
2018-04-09 13:57 ` Salvatore Mesoraca
2018-04-09 14:02 ` Salvatore Mesoraca
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=1523126303-23205-1-git-send-email-s.mesoraca16@gmail.com \
--to=s.mesoraca16@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®