[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181120054830.rfgoaz37iogqk3sg@gondor.apana.org.au>
Date: Tue, 20 Nov 2018 13:48:30 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: LABBE Corentin <clabbe@...libre.com>
Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Biggers <ebiggers@...nel.org>, nhorman@...driver.com,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 01/11] crypto: move crypto_alg_get/crypto_alg_put to
linux/crypto.h
On Tue, Nov 20, 2018 at 06:46:59AM +0100, LABBE Corentin wrote:
> On Tue, Nov 20, 2018 at 11:10:47AM +0800, Herbert Xu wrote:
> > On Mon, Nov 19, 2018 at 12:25:10PM -0800, Ard Biesheuvel wrote:
> > > On Mon, 19 Nov 2018 at 11:53, Corentin Labbe <clabbe@...libre.com> wrote:
> > > >
> > > > Since we will need crypto_alg_get/crypto_alg_put for "locking"
> > > > crypto_alg when updating stats, we need it to be via linux/crypto.h
> > > >
> > >
> > > This seems backwards to me. Surely, crypto stats are permitted to use
> > > the internal crypto API?
> >
> > I agree.
> >
>
> I dont understand what is backwards ? moving or using ?
> What do you suggest for "locking" crypto_alg ?
You should include "crypto/internal.h" directly in your code rather
than exporting these functions for wider usage outside of the API
code.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists