IBM Z Crypto Express (CEX) hardware security modules
Support for IBM Z mainframe Crypto Express adapters and the Adjunct Processor bus that connects them. These cryptographic coprocessors and hardware security modules accelerate RSA, ECC, and symmetric crypto in accelerator, CCA, or EP11 modes, and are standard equipment on current IBM z16 and z17 systems used by banks, governments, and other regulated Linux-on-Z workloads.
recommendation
It should stay because the hardware still ships on IBM's current z16 and z17 mainframes, the directory sees sustained upstream development with patches landing as recently as 2026, and nothing else in the kernel covers the AP bus, zcrypt, pkey, or vfio_ap stack. The on-CPU CPACF facility is a separate feature, not a replacement, so this is a clear keep for any kernel used on IBM Z.
repository signals
sources
- lore.kernel.org
The subsystem is still receiving upstream work in 2026; a March 24, 2026 patch touched ap_bus.c ('s390/ap: use generic driver_override infrastructure').
- ibm.com
IBM z16 product material explicitly references the Crypto Express 8S card, showing Crypto Express hardware remained part of current IBM Z offerings in the z16 generation.
- ibm.com
IBM z17 HMC documentation describes configuring and monitoring installed Crypto Express features as current system hardware, indicating ongoing availability/use in the z17 generation.
- ibm.com
IBM Linux on Z documentation describes Crypto Express adapters, their accelerator/CCA/EP11 modes, and AP queues, matching this driver's hardware scope and showing it remains a supported Linux-on-IBM-Z feature.
codex reasoning notes (technical)
Real driver directory: contains AP bus, zcrypt, pkey, and vfio_ap driver code. lore_file_timeline tool on drivers/s390/crypto/ap_bus.c showed sustained activity through 2026-03-24 with hundreds of touches in the last 5 years; that argues strongly against deprecation/removal. Web search found IBM z16 product material and IBM z17/HMC + Linux-on-Z docs showing Crypto Express is still present in current IBM Z generations, so hardware is still sold and deployed. No natural upstream replacement driver covers the same AP/Crypto Express/HSM stack; CPACF is a different facility, not a drop-in replacement. Removal-talk absence is an inference from active lore traffic plus failed/empty targeted removal-search attempts, not a direct cited negative proof.