public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 4/10] crypto: hash - Count error stats differently
Date: Wed, 15 Feb 2023 21:58:57 -0800	[thread overview]
Message-ID: <Y+3GIaoMR+2mzAmi@sol.localdomain> (raw)
In-Reply-To: <E1pSE2L-00BVkw-GI@formenos.hmeau.com>

On Wed, Feb 15, 2023 at 05:25:13PM +0800, Herbert Xu wrote:
> Move all stat code specific to hash into the hash code.
> 
> While we're at it, change the stats so that bytes and counts
> are always incremented even in case of error.  This allows the
> reference counting to be removed as we can now increment the
> counters prior to the operation.
> 
> After the operation we simply increase the error count if necessary.
> This is safe as errors can only occur synchronously (or rather,
> the existing code already ignored asynchronous errors which are
> only visible to the callback function).
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> ---
> 
>  crypto/ahash.c            |   82 +++++++++++++++++------------
>  crypto/algapi.c           |   24 --------
>  crypto/crypto_user_stat.c |   38 -------------
>  crypto/hash.h             |   37 +++++++++++++
>  crypto/shash.c            |  128 ++++++++++++++++++++++++++++++++++++----------
>  include/crypto/hash.h     |   85 +++++++++++++++++++++++-------
>  include/linux/crypto.h    |   20 -------
>  7 files changed, 250 insertions(+), 164 deletions(-)

This patch is causing the 'BUG_ON(refcount_read(&alg->cra_refcnt) != 1);' in
crypto_unregister_alg() to be hit at boot time.

Most likely related to the way the algorithm structs are being rearranged (which
really ought to be explained in the commit message).

- Eric

  reply	other threads:[~2023-02-16  5:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  9:24 [PATCH 0/10] crypto: api - Restructure stats code Herbert Xu
2023-02-15  9:25 ` [PATCH 1/10] crypto: algapi - Move stat reporting into algapi Herbert Xu
2023-02-15  9:25 ` [PATCH 2/10] crypto: aead - Count error stats differently Herbert Xu
2023-02-16  5:35   ` Eric Biggers
2023-02-16  5:58     ` Herbert Xu
2023-02-16  5:45   ` Eric Biggers
2023-02-16  6:00     ` Herbert Xu
2023-02-16  6:31       ` Eric Biggers
2023-02-16  8:34         ` Herbert Xu
2023-02-15  9:25 ` [PATCH 3/10] crypto: akcipher " Herbert Xu
2023-02-15  9:25 ` [PATCH 4/10] crypto: hash " Herbert Xu
2023-02-16  5:58   ` Eric Biggers [this message]
2023-02-16  6:02     ` Herbert Xu
2023-02-16  6:14       ` Eric Biggers
2023-02-16  8:09         ` Herbert Xu
2023-02-15  9:25 ` [PATCH 5/10] crypto: acomp " Herbert Xu
2023-02-15  9:25 ` [PATCH 6/10] crypto: kpp " Herbert Xu
2023-02-15  9:25 ` [PATCH 7/10] crypto: skcipher " Herbert Xu
2023-02-15  9:25 ` [PATCH 8/10] crypto: rng " Herbert Xu
2023-02-16  5:46   ` Eric Biggers
2023-02-16  5:56     ` Herbert Xu
2023-02-16  6:01       ` Eric Biggers
2023-02-15  9:25 ` [PATCH 9/10] crypto: api - Move MODULE_ALIAS_CRYPTO to algapi.h Herbert Xu
2023-02-16  5:17   ` Eric Biggers
2023-02-16  5:18     ` Herbert Xu
2023-02-15  9:25 ` [PATCH 10/10] crypto: api - Check CRYPTO_USER instead of NET for report Herbert Xu

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=Y+3GIaoMR+2mzAmi@sol.localdomain \
    --to=ebiggers@kernel.org \
    --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