All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Dengler <dengler@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	sparclinux@vger.kernel.org, x86@kernel.org,
	Harald Freudenberger <freude@linux.ibm.com>
Subject: Re: [PATCH 1/3] crypto: s390 - Remove des and des3_ede code
Date: Fri, 27 Mar 2026 09:52:31 +0100	[thread overview]
Message-ID: <65c3d229-57ee-4980-a13f-bc9661b4dda1@linux.ibm.com> (raw)
In-Reply-To: <20260326201246.57544-2-ebiggers@kernel.org>

Hi Eric,

On 26/03/2026 21:12, Eric Biggers wrote:
> Since DES and Triple DES are obsolete, there is very little point in
> maintining architecture-optimized code for them.  Remove it.
> 
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>

Are there plans to completely remove des/3des in-kernel crypto support from
the kernel or is it just the arch-specific code, that is removed?

In fact there are still customers using des/3des (unbelievable!), but the
valid question is, do they also using the in-kernel crypto for their
workloads. I'll try to figure that out. Unfortunately, Harald is a few days
off and I need to discuss the removal with him as well.

Regarding the testing: in our CI we're running all in-kernel crypto modules
every night, including des/3des. So there is some test coverage.

Regarding qemu: we're currently investigating if we can provide qemu-support
for the s390 crypto instructions, but, to be honest, des/3des was not on our
top-priority list until now... ;)

We'll come back to you in a week or so. I hope, that's ok...

-- 
Mit freundlichen Grüßen / Kind regards
Holger Dengler
--
IBM Systems, Linux on IBM Z Development
dengler@linux.ibm.com


  reply	other threads:[~2026-03-27  8:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 20:12 [PATCH 0/3] crypto: Remove arch-optimized des and des3_ede code Eric Biggers
2026-03-26 20:12 ` [PATCH 1/3] crypto: s390 - Remove " Eric Biggers
2026-03-27  8:52   ` Holger Dengler [this message]
2026-03-27 17:32     ` Eric Biggers
2026-04-09 11:02       ` Harald Freudenberger
2026-04-09  7:08   ` Holger Dengler
2026-04-09  7:29     ` John Paul Adrian Glaubitz
2026-04-09  8:22       ` Holger Dengler
2026-04-09 17:48         ` Eric Biggers
2026-03-26 20:12 ` [PATCH 2/3] crypto: sparc " Eric Biggers
2026-03-26 20:12 ` [PATCH 3/3] crypto: x86 " Eric Biggers
2026-03-26 20:20 ` [PATCH 0/3] crypto: Remove arch-optimized " John Paul Adrian Glaubitz
2026-03-26 20:27   ` Eric Biggers
2026-03-26 21:07     ` Eric Biggers
2026-03-27  9:59     ` Simon Richter
2026-03-27 17:24       ` Eric Biggers
2026-04-09 12:46         ` Ard Biesheuvel
2026-04-08 13:35   ` Harald Freudenberger
2026-04-08 13:43     ` John Paul Adrian Glaubitz
2026-04-03  1:07 ` 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=65c3d229-57ee-4980-a13f-bc9661b4dda1@linux.ibm.com \
    --to=dengler@linux.ibm.com \
    --cc=ebiggers@kernel.org \
    --cc=freude@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=x86@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.