From: Salvatore Mesoraca <s.mesoraca16@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Kees Cook <keescook@chromium.org>,
Eric Biggers <ebiggers3@gmail.com>,
Laura Abbott <labbott@redhat.com>
Subject: Re: [PATCH v2 0/2] crypto: removing various VLAs
Date: Thu, 26 Apr 2018 19:27:07 +0200 [thread overview]
Message-ID: <CAJHCu1LDTDD5pBJYbsiio5yne-a+cVgDLaVNYSKxjq=L74JWqQ@mail.gmail.com> (raw)
In-Reply-To: <20180420165143.mwcxwkf6j7ddckdt@gondor.apana.org.au>
2018-04-20 18:51 GMT+02:00 Herbert Xu <herbert@gondor.apana.org.au>:
> On Mon, Apr 09, 2018 at 03:54:45PM +0200, Salvatore Mesoraca wrote:
>> v2:
>> As suggested by Herbert Xu, the blocksize and alignmask checks
>> have been moved to crypto_check_alg.
>> So, now, all the other separate checks are not necessary.
>> Also, the defines have been moved to include/crypto/algapi.h.
>>
>> v1:
>> As suggested by Laura Abbott[1], I'm resending my patch with
>> MAX_BLOCKSIZE and MAX_ALIGNMASK defined in an header, so they
>> can be used in other places.
>> I took this opportunity to deal with some other VLAs not
>> handled in the old patch.
>>
>> [1] http://lkml.kernel.org/r/4e536889-439a-49e6-dd95-2d4286913202@redhat.com
>>
>> Salvatore Mesoraca (2):
>> crypto: api - laying defines and checks for statically allocated
>> buffers
>> crypto: remove several VLAs
>>
>> crypto/algapi.c | 10 ++++++++++
>> crypto/cfb.c | 7 +++----
>> crypto/cipher.c | 3 ++-
>> crypto/ctr.c | 4 ++--
>> crypto/cts.c | 5 +++--
>> crypto/pcbc.c | 5 +++--
>> include/crypto/algapi.h | 8 ++++++++
>> 7 files changed, 31 insertions(+), 11 deletions(-)
>
> All applied. Thanks.
Thank you very much.
Salvatore
prev parent reply other threads:[~2018-04-26 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 13:54 [PATCH v2 0/2] crypto: removing various VLAs Salvatore Mesoraca
2018-04-09 13:54 ` [PATCH v2 1/2] crypto: api - laying defines and checks for statically allocated buffers Salvatore Mesoraca
2018-04-09 13:54 ` [PATCH v2 2/2] crypto: remove several VLAs Salvatore Mesoraca
2018-04-09 14:35 ` [PATCH v2 0/2] crypto: removing various VLAs David Laight
2018-04-09 16:38 ` Salvatore Mesoraca
2018-04-11 16:20 ` David Laight
2018-04-20 16:51 ` Herbert Xu
2018-04-26 17:27 ` Salvatore Mesoraca [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='CAJHCu1LDTDD5pBJYbsiio5yne-a+cVgDLaVNYSKxjq=L74JWqQ@mail.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;
as well as URLs for NNTP newsgroup(s).