All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	herbert@gondor.apana.org.au, linux-s390@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH v7 0/9] Fixes and rework for paes_s390 and phmac_s390
Date: Thu, 3 Sep 2026 21:36:03 +0200	[thread overview]
Message-ID: <20260903193603.12158E8b-hca@linux.ibm.com> (raw)
In-Reply-To: <20260831083838.3703-1-freude@linux.ibm.com>

On Mon, Aug 31, 2026 at 10:38:29AM +0200, Harald Freudenberger wrote:
> Fix and rework some issues around arch/s390/paes_s390.c and
> arch/s390/phmac_s390.c:
> 
> - Fix skcipher_walk return code handling in paes_s390
> - Add scrub of some temp buffers
> - Shift from using a mutex to using a semaphore in PAES CTR
>   Surprisingly clang code analysis is able to deal with semaphores and
>   thus the shift also fixes the issue with CONTEXT_ANALYSIS enabled.
> - And some more fixes related to paes and phmac (see changelog).
...
> Harald Freudenberger (8):
>   s390/crypto: Fix return code handling at skcipher_walk_done in PAES
>     algorithms
>   s390/crypto: Fix missing scrub of temp buffers with PAES algorithm
>   s390/crypto: Fix use of mutex in atomic context in PAES
>   s390/crypto: Fix missing cra_flags in paes_s390
>   s390/crypto: Fix handling of EBUSY in PAES when req is pushed to
>     crypto engine
>   s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to
>     crypto engine
>   s390/crypto: Fix wrong return code to engine in asynch callbacks
>   s390/crypto: Map EBUSY to EIO when key conversion fails repeatedly
> 
> Heiko Carstens (1):
>   s390/crypto: Enable CONTEXT_ANALYSIS
> 
>  arch/s390/crypto/Makefile     |   2 +
>  arch/s390/crypto/paes_s390.c  | 184 +++++++++++++++++++++-------------
>  arch/s390/crypto/phmac_s390.c |  36 +++++--
>  3 files changed, 142 insertions(+), 80 deletions(-)

Applied, thanks.

FWIW, since there was some confusion about CONTEXT_ANALYSIS and if
this should go upstream via s390 or crypto, I applied this now to
s390. Future crypto patches should go via the crypto tree again.

      parent reply	other threads:[~2026-09-03 19:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  8:38 [PATCH v7 0/9] Fixes and rework for paes_s390 and phmac_s390 Harald Freudenberger
2026-08-31  8:38 ` [PATCH v7 1/9] s390/crypto: Fix return code handling at skcipher_walk_done in PAES algorithms Harald Freudenberger
2026-08-31  8:55   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 2/9] s390/crypto: Fix missing scrub of temp buffers with PAES algorithm Harald Freudenberger
2026-08-31  9:10   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 3/9] s390/crypto: Fix use of mutex in atomic context in PAES Harald Freudenberger
2026-08-31  9:19   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 4/9] s390/crypto: Fix missing cra_flags in paes_s390 Harald Freudenberger
2026-08-31  9:32   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 5/9] s390/crypto: Fix handling of EBUSY in PAES when req is pushed to crypto engine Harald Freudenberger
2026-08-31  9:45   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 6/9] s390/crypto: Fix handling of EBUSY in PHMAC " Harald Freudenberger
2026-08-31  9:58   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 7/9] s390/crypto: Fix wrong return code to engine in asynch callbacks Harald Freudenberger
2026-08-31 10:04   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 8/9] s390/crypto: Map EBUSY to EIO when key conversion fails repeatedly Harald Freudenberger
2026-08-31 10:10   ` sashiko-bot
2026-08-31  8:38 ` [PATCH v7 9/9] s390/crypto: Enable CONTEXT_ANALYSIS Harald Freudenberger
2026-08-31 10:11   ` sashiko-bot
2026-09-03 19:36 ` Heiko Carstens [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=20260903193603.12158E8b-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-s390@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.