From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: algif_aead - Require setkey before accept(2)
Date: Fri, 21 Apr 2017 18:35:07 +0200 [thread overview]
Message-ID: <2572320.UaipMWf1ob@positron.chronox.de> (raw)
In-Reply-To: <20170421111127.GA13925@gondor.apana.org.au>
Am Freitag, 21. April 2017, 13:11:27 CEST schrieb Herbert Xu:
Hi Herbert,
> On Mon, Apr 10, 2017 at 01:59:21PM +0200, Stephan Müller wrote:
> > @@ -757,12 +887,14 @@ static void aead_sock_destruct(struct sock *sk)
> >
> > af_alg_release_parent(sk);
> >
> > }
> >
> > -static int aead_accept_parent(void *private, struct sock *sk)
> > +static int aead_accept_parent_nokey(void *private, struct sock *sk)
> >
> > {
> >
> > struct aead_ctx *ctx;
> > struct alg_sock *ask = alg_sk(sk);
> >
> > - unsigned int len = sizeof(*ctx) + crypto_aead_reqsize(private);
> > - unsigned int ivlen = crypto_aead_ivsize(private);
> > + struct aead_tfm *tfm = private;
> > + struct crypto_aead *aead = tfm->aead;
> > + unsigned int len = sizeof(*ctx) + crypto_aead_reqsize(aead);
> > + unsigned int ivlen = crypto_aead_ivsize(aead);
> >
> > ctx = sock_kmalloc(sk, len, GFP_KERNEL);
> > if (!ctx)
> >
> > @@ -789,7 +921,7 @@ static int aead_accept_parent(void *private, struct
> > sock *sk)>
> > ask->private = ctx;
> >
> > - aead_request_set_tfm(&ctx->aead_req, private);
> > + aead_request_set_tfm(&ctx->aead_req, aead);
> >
> > aead_request_set_callback(&ctx->aead_req, CRYPTO_TFM_REQ_MAY_BACKLOG,
> >
> > af_alg_complete, &ctx->completion);
>
> Please don't mix unrelated cleanups like this with the real change.
> It makes reviewing harder than necessary.
>
After checking again, IMHO that is no unreleated cleanup or even a cleanup at
all.
void *private used to be struct crypto_aead and is now struct aead_tfm. struct
crypto_aead is found in private->aead. Hence, the patch assigned private to
tfm and then obtained the struct crypto_aead pointer. As this was not
necessary before, it is a required extension IMHO.
Ciao
Stephan
next prev parent reply other threads:[~2017-04-21 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 11:59 [PATCH] crypto: algif_aead - Require setkey before accept(2) Stephan Müller
2017-04-21 11:11 ` Herbert Xu
2017-04-21 15:33 ` Stephan Müller
2017-04-21 16:35 ` Stephan Müller [this message]
2017-04-24 8:43 ` Herbert Xu
2017-04-24 9:01 ` Stephan Müller
2017-04-24 9:03 ` Herbert Xu
2017-04-24 9:15 ` [PATCH v2] " Stephan Müller
2017-04-24 10:22 ` Herbert Xu
2017-04-24 10:26 ` Stephan Müller
2017-04-25 8:47 ` Herbert Xu
2017-04-25 8:54 ` Stephan Müller
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=2572320.UaipMWf1ob@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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).