From: Kees Cook <keescook@chromium.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>,
Roland Kammerer <roland.kammerer@linbit.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Eric Biggers <ebiggers@google.com>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] [v2] drbd: dynamically allocate shash descriptor
Date: Mon, 22 Jul 2019 09:52:30 -0700 [thread overview]
Message-ID: <201907220952.EA05EEE9FC@keescook> (raw)
In-Reply-To: <20190722122647.351002-1-arnd@arndb.de>
On Mon, Jul 22, 2019 at 02:26:34PM +0200, Arnd Bergmann wrote:
> Building with clang and KASAN, we get a warning about an overly large
> stack frame on 32-bit architectures:
>
> drivers/block/drbd/drbd_receiver.c:921:31: error: stack frame size of 1280 bytes in function 'conn_connect'
> [-Werror,-Wframe-larger-than=]
>
> We already allocate other data dynamically in this function, so
> just do the same for the shash descriptor, which makes up most of
> this memory.
>
> Link: https://lore.kernel.org/lkml/20190617132440.2721536-1-arnd@arndb.de/
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> v2:
> - don't try to zero a NULL descriptor pointer,
> based on review from Roland Kammerer.
> ---
> drivers/block/drbd/drbd_receiver.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/block/drbd/drbd_receiver.c b/drivers/block/drbd/drbd_receiver.c
> index 90ebfcae0ce6..2b3103c30857 100644
> --- a/drivers/block/drbd/drbd_receiver.c
> +++ b/drivers/block/drbd/drbd_receiver.c
> @@ -5417,7 +5417,7 @@ static int drbd_do_auth(struct drbd_connection *connection)
> unsigned int key_len;
> char secret[SHARED_SECRET_MAX]; /* 64 byte */
> unsigned int resp_size;
> - SHASH_DESC_ON_STACK(desc, connection->cram_hmac_tfm);
> + struct shash_desc *desc;
> struct packet_info pi;
> struct net_conf *nc;
> int err, rv;
> @@ -5430,6 +5430,13 @@ static int drbd_do_auth(struct drbd_connection *connection)
> memcpy(secret, nc->shared_secret, key_len);
> rcu_read_unlock();
>
> + desc = kmalloc(sizeof(struct shash_desc) +
> + crypto_shash_descsize(connection->cram_hmac_tfm),
> + GFP_KERNEL);
> + if (!desc) {
> + rv = -1;
> + goto fail;
> + }
> desc->tfm = connection->cram_hmac_tfm;
>
> rv = crypto_shash_setkey(connection->cram_hmac_tfm, (u8 *)secret, key_len);
> @@ -5571,7 +5578,10 @@ static int drbd_do_auth(struct drbd_connection *connection)
> kfree(peers_ch);
> kfree(response);
> kfree(right_response);
> - shash_desc_zero(desc);
> + if (desc) {
> + shash_desc_zero(desc);
> + kfree(desc);
> + }
>
> return rv;
> }
> --
> 2.20.0
>
--
Kees Cook
next prev parent reply other threads:[~2019-07-22 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 12:26 [PATCH] [v2] drbd: dynamically allocate shash descriptor Arnd Bergmann
2019-07-22 16:52 ` Kees Cook [this message]
2019-07-23 7:47 ` Roland Kammerer
2019-07-23 13:35 ` Jens Axboe
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=201907220952.EA05EEE9FC@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=clang-built-linux@googlegroups.com \
--cc=drbd-dev@lists.linbit.com \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=roland.kammerer@linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox