Changes in Kconfig

e7f57d2c47e265ef64e1dab84fc8f70dae2dd150 - dm-inlinecrypt: add target for inline block device encryption

Thu, 30 Apr 2026 11:52:43 +0200

dm-inlinecrypt: add target for inline block device encryptionAdd a new device-mapper target "dm-inlinecrypt" that is similar todm-crypt but uses the blk-crypto API instead of the regular crypto API.This allows it to take advantage of inline encryption hardware such asthat commonly built into UFS host controllers.The table syntax matches dm-crypt's, but for now only a stripped-downset of parameters is supported. For example, for now AES-256-XTS is theonly supported cipher.dm-inlinecrypt is based on Android's dm-default-key with thecontroversial passthrough support removed. Note that due to the removalof passthrough support, use of dm-inlinecrypt in combination withfscrypt causes double encryption of file contents (similar to dm-crypt +fscrypt), with the fscrypt layer not being able to use the inlineencryption hardware. This makes dm-inlinecrypt unusable on systems suchas Android that use fscrypt and where a more optimized approach isneeded. It is however suitable as a replacement for dm-crypt.dm-inlinecrypt supports both keyring key and hex key, the former avoidsthe key to be exposed in dm-table message. Similar to dm-default-key inAndroid, it will fallabck to the software block crypto once the inlinecrypto hardware cannot support the expected cipher.Test:dmsetup create inlinecrypt_logon --table "0 `blockdev --getsz $1` \inlinecrypt aes-xts-plain64 :64:logon:fde:dminlinecrypt_test_key 0 $1 0"Signed-off-by: Eric Biggers Signed-off-by: Linlin Zhang Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

d1c3b6b8e74393a5b34b91a056bd7ea6ae33938a - dm-crypt: Reimplement elephant diffuser using AES library

Sun, 22 Mar 2026 00:06:50 +0100

dm-crypt: Reimplement elephant diffuser using AES librarySimplify and optimize dm-crypt's implementation of Bitlocker's "elephantdiffuser" to use the AES library instead of an "ecb(aes)"crypto_skcipher.Note: struct aes_enckey is fixed-size, so it could be embedded directlyin struct iv_elephant_private. But I kept it as a separate allocationso that the size of struct crypt_config doesn't increase. The elephantdiffuser is rarely used in dm-crypt.Signed-off-by: Eric Biggers Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

5282ac80183bd25e44c4f5f52a7f46e9a54289eb - dm-ima: use SHA-256 library

Thu, 26 Feb 2026 02:39:15 +0100

dm-ima: use SHA-256 libraryMake dm_ima_measure_on_table_load() use the SHA-256 library API insteadof crypto_shash to calculate the SHA-256 hash value that it needs. Thisis simpler and more efficient. It also ensures that SHA-256 is actuallyavailable and doesn't fail due to the unreliable loading by name.While doing this, also use kasprintf() to simplify building the stringversion of the digest.Signed-off-by: Eric Biggers Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

8fbb8fe75d4cf92eaa7b21828ec39c1bf79a262f - dm-verity: allow REED_SOLOMON to be 'm' if DM_VERITY is 'm'

Fri, 19 Dec 2025 20:29:09 +0100

dm-verity: allow REED_SOLOMON to be 'm' if DM_VERITY is 'm'The dm-verity kconfig options make the common mistake of selecting adependency from a bool "sub-option" rather than the main tristateoption. This unnecessarily forces the dependency to built-in ('y').Fix this by moving the selections of REED_SOLOMON and REED_SOLOMON_DEC8into DM_VERITY, conditional on DM_VERITY_FEC.This allows REED_SOLOMON to be 'm' if DM_VERITY is 'm'.Reviewed-by: Sami Tolvanen Signed-off-by: Eric Biggers Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

ba0f428c9b40364f1af92523860c787068987b8c - dm-verity: use SHA-256 library for SHA-256

Tue, 14 Oct 2025 23:16:55 +0200

dm-verity: use SHA-256 library for SHA-256When the hash algorithm is SHA-256 and the verity version is not 0, usethe SHA-256 library instead of crypto_shash.This is a prerequisite for making dm-verity interleave the computationof SHA-256 hashes for increased performance. That optimization isavailable in the SHA-256 library but not in crypto_shash.Even without interleaved hashing, switching to the library also slightlyimproves performance by itself because it avoids the overhead ofcrypto_shash, including indirect calls and other API overhead.(Benchmark on x86_64, AMD Zen 5: hashing 4K blocks gets 2.1% faster.)SHA-256 is by far the most common hash algorithm used with dm-verity.It makes sense to optimize for the common case and fall back to thegeneric crypto layer for uncommon cases, as suggested by Linus:https://lore.kernel.org/r/CAHk-=wgp-fOSsZsYrbyzqCAfEvrt5jQs1jL-97Wc4seMNTUyng@mail.gmail.comSigned-off-by: Eric Biggers Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

ba59e59b8b4dc0cb4882aa6f91fe16361dd95b99 - dm-crypt: Use MD5 library instead of crypto_shash

Sat, 11 Oct 2025 20:10:42 +0200

dm-crypt: Use MD5 library instead of crypto_shashThe lmk IV mode, which dm-crypt supports for Loop-AES compatibility,involves an MD5 computation. Update its implementation to use the MD5library API instead of crypto_shash. This has many benefits, such as:- Simpler code. Notably, much of the error-handling code is no longer needed, since the library functions can't fail.- Reduced stack usage. crypt_iv_lmk_one() now allocates only 112 bytes on the stack instead of 520 bytes.- The library functions are strongly typed, preventing bugs like https://lore.kernel.org/r/f1625ddc-e82e-4b77-80c2-dc8e45b54848@gmail.com- Slightly improved performance, as the library provides direct access to the MD5 code without unnecessary overhead such as indirect calls.To preserve the existing behavior of lmk support being disabled when thekernel is booted with "fips=1", make crypt_iv_lmk_ctr() checkfips_enabled itself. Previously it relied on crypto_alloc_shash("md5")failing. (I don't know for sure that lmk *actually* needs to bedisallowed in FIPS mode; this just preserves the existing behavior.)Signed-off-by: Eric Biggers Signed-off-by: Mikulas Patocka Acked-by: Ard Biesheuvel List of files: /linux/drivers/md/Kconfig

7dbec0bbc3b468310be172f1ce6ddc9411c84952 - Merge tag 'for-6.18/dm-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm

Sat, 04 Oct 2025 03:48:02 +0200

Merge tag 'for-6.18/dm-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dmPull device mapper updates from Mikulas Patocka: - a new dm-pcache target for read/write caching on persistent memory - fix typos in docs - misc small refactoring - mark dm-error with DM_TARGET_PASSES_INTEGRITY - dm-request-based: fix NULL pointer dereference and quiesce_depth out of sync - dm-linear: optimize REQ_PREFLUSH - dm-vdo: return error on corrupted metadata - dm-integrity: support asynchronous hash interface* tag 'for-6.18/dm-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm: (27 commits) dm raid: use proper md_ro_state enumerators dm-integrity: prefer synchronous hash interface dm-integrity: enable asynchronous hash interface dm-integrity: rename internal_hash dm-integrity: add the "offset" argument dm-integrity: allocate the recalculate buffer with kmalloc dm-integrity: introduce integrity_kmap and integrity_kunmap dm-integrity: replace bvec_kmap_local with kmap_local_page dm-integrity: use internal variable for digestsize dm vdo: return error on corrupted metadata in start_restoring_volume functions dm vdo: Update code to use mem_is_zero dm: optimize REQ_PREFLUSH with data when using the linear target dm-pcache: use int type to store negative error codes dm: fix "writen"->"written" dm-pcache: cleanup: fix coding style report by checkpatch.pl dm-pcache: remove ctrl_lock for pcache_cache_segment dm: fix NULL pointer dereference in __dm_suspend() dm: fix queue start/stop imbalance under suspend/load/resume races dm-pcache: add persistent cache target in device-mapper dm error: mark as DM_TARGET_PASSES_INTEGRITY ... List of files: /linux/drivers/md/Kconfig

5ab829f1971dc99f2aac10846c378e67fc875abc - md/md-llbitmap: introduce new lockless bitmap

Fri, 29 Aug 2025 10:04:26 +0200

md/md-llbitmap: introduce new lockless bitmapRedundant data is used to enhance data fault tolerance, and the storagemethod for redundant data vary depending on the RAID levels. And it'simportant to maintain the consistency of redundant data.Bitmap is used to record which data blocks have been synchronized and whichones need to be resynchronized or recovered. Each bit in the bitmaprepresents a segment of data in the array. When a bit is set, it indicatesthat the multiple redundant copies of that data segment may not beconsistent. Data synchronization can be performed based on the bitmap afterpower failure or readding a disk. If there is no bitmap, a full disksynchronization is required.Due to known performance issues with md-bitmap and the unreasonableimplementations: - self-managed IO submitting like filemap_write_page(); - global spin_lockI have decided not to continue optimizing based on the current bitmapimplementation, this new bitmap is invented without locking from IO fastpath and can be used with fast disks.For designs and details, see the comments in drivers/md-llbitmap.c.Link: https://lore.kernel.org/linux-raid/20250829080426.1441678-12-yukuai1@huaweicloud.comSigned-off-by: Yu Kuai Reviewed-by: Li Nan List of files: /linux/drivers/md/Kconfig

c27474ac1d4609af3c1c38ccac252c2575b47b9e - md/md-bitmap: introduce CONFIG_MD_BITMAP

Mon, 07 Jul 2025 03:27:11 +0200

md/md-bitmap: introduce CONFIG_MD_BITMAPNow that all implementations are internal, it's sensible to add a configoption for md-bitmap, and it's a good way for isolation.Link: https://lore.kernel.org/linux-raid/20250707012711.376844-16-yukuai1@huaweicloud.comSigned-off-by: Yu Kuai Reviewed-by: Xiao Ni List of files: /linux/drivers/md/Kconfig

1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 - dm-pcache: add persistent cache target in device-mapper

Tue, 12 Aug 2025 10:24:52 +0200

dm-pcache: add persistent cache target in device-mapperThis patch introduces dm-pcache, a new DM target that places a DAX-capable persistent-memory device in front of any slower block device anduses it as a high-throughput, low-latency cache.Design highlights------------------ DAX data path – data is copied directly between DRAM and the pmem mapping, bypassing the block layer’s overhead.- Segmented, crash-consistent layout - all layout metadata are dual-replicated CRC-protected. - atomic kset flushes; key replay on mount guarantees cache integrity even after power loss.- Striped multi-tree index - Multi‑tree indexing for high parallelism. - overlap-resolution logic ensures non-intersecting cached extents.- Background services - write-back worker flushes dirty keys in order, preserving backing-device crash consistency. This is important for checkpoint in cloud storage. - garbage collector reclaims clean segments when utilisation exceeds a tunable threshold.- Data integrity – optional CRC32 on cached payload; metadata always protected.Comparison with existing block-level caches---------------------------------------------------------------------------------------------------------------------------------| Feature | pcache (this patch) | bcache | dm-writecache ||----------------------------------|---------------------------------|------------------------------|---------------------------|| pmem access method | DAX | bio (block I/O) | DAX || Write latency (4 K rand-write) | ~5 µs | ~20 µs | ~5 µs || Concurrency | multi subtree index | global index tree | single tree + wc_lock || IOPS (4K randwrite, 32 numjobs) | 2.1 M | 352 K | 283 K || Read-cache support | YES | YES | NO || Deployment | no re-format of backend | backend devices must be | no re-format of backend || | | reformatted | || Write-back ordering | log-structured; | no ordering guarantee | no ordering guarantee || | preserves app-IO-order | | || Data integrity checks | metadata + data CRC(optional) | metadata CRC only | none |---------------------------------------------------------------------------------------------------------------------------------Signed-off-by: Dongsheng Yang Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

97c484ccb804ac07f8be80d66a250a260cc9339e - Merge tag 'crc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux

Tue, 08 Apr 2025 21:09:28 +0200

Merge tag 'crc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linuxPull CRC cleanups from Eric Biggers: "Finish cleaning up the CRC kconfig options by removing the remaining unnecessary prompts and an unnecessary 'default y', removing CONFIG_LIBCRC32C, and documenting all the CRC library options"* tag 'crc-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux: lib/crc: remove CONFIG_LIBCRC32C lib/crc: document all the CRC library kconfig options lib/crc: remove unnecessary prompt for CONFIG_CRC_ITU_T lib/crc: remove unnecessary prompt for CONFIG_CRC_T10DIF lib/crc: remove unnecessary prompt for CONFIG_CRC16 lib/crc: remove unnecessary prompt for CONFIG_CRC_CCITT lib/crc: remove unnecessary prompt for CONFIG_CRC32 and drop 'default y' List of files: /linux/drivers/md/Kconfig

b261d2222063a9a8b9ec284244c285f2998ee01e - lib/crc: remove CONFIG_LIBCRC32C

Wed, 02 Apr 2025 00:16:00 +0200

lib/crc: remove CONFIG_LIBCRC32CNow that LIBCRC32C does nothing besides select CRC32, make every optionthat selects LIBCRC32C instead select CRC32 directly. Then removeLIBCRC32C.Reviewed-by: Christoph Hellwig Reviewed-by: "Martin K. Petersen" Acked-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20250401221600.24878-8-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/drivers/md/Kconfig

f656fa4013388a52d1fdd82268955c5e7be63ad2 - dm-crypt: switch to using the crc32 library

Mon, 27 Jan 2025 23:15:33 +0100

dm-crypt: switch to using the crc32 libraryNow that the crc32() library function takes advantage ofarchitecture-specific optimizations, it is unnecessary to go through thecrypto API. Just use crc32(). This is much simpler, and it improvesperformance due to eliminating the crypto API overhead. (However, thisonly affects the TCW IV mode of dm-crypt, which is a compatibility modethat is rarely used compared to other dm-crypt modes.)Signed-off-by: Eric Biggers Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

127186cfb184eaccdfe948e6da66940cfa03efc5 - md: reintroduce md-linear

Thu, 02 Jan 2025 12:28:41 +0100

md: reintroduce md-linearTHe md-linear is removed by commit 849d18e27be9 ("md: Remove deprecatedCONFIG_MD_LINEAR") because it has been marked as deprecated for a longtime.However, md-linear is used widely for underlying disks with different size,sadly we didn't know this until now, and it's true useful to createpartitions and assemble multiple raid and then append one to the other.People have to use dm-linear in this case now, however, they will preferto minimize the number of involved modules.Fixes: 849d18e27be9 ("md: Remove deprecated CONFIG_MD_LINEAR")Cc: stable@vger.kernel.orgSigned-off-by: Yu Kuai Acked-by: Coly Li Acked-by: Mike Snitzer Link: https://lore.kernel.org/r/20250102112841.1227111-1-yukuai1@huaweicloud.comSigned-off-by: Song Liu List of files: /linux/drivers/md/Kconfig

6fce1f40e95182ebbfe1ee3096b8fc0b37903269 - dm verity: add support for signature verification with platform keyring

Tue, 02 Jul 2024 18:16:57 +0200

dm verity: add support for signature verification with platform keyringAdd a new configuration CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_PLATFORM_KEYRINGthat enables verifying dm-verity signatures using the platform keyring,which is populated using the UEFI DB certificates. This is useful forself-enrolled systems that do not use MOK, as the secondary keyring whichis already used for verification, if the relevant kconfig is enabled, islinked to the machine keyring, which gets its certificates loaded from MOK.On datacenter/virtual/cloud deployments it is more common to deploy one'sown certificate chain directly in DB on first boot in unattended mode,rather than relying on MOK, as the latter typically requires interactiveauthentication to enroll, and is more suited for personal machines.Default to the same value as DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRINGif not otherwise specified, as it is likely that if one wants to useMOK certificates to verify dm-verity volumes, DB certificates aregoing to be used too. Keys in DB are allowed to load a full kernelalready anyway, so they are already highly privileged.Signed-off-by: Luca Boccassi Signed-off-by: Mikulas Patocka List of files: /linux/drivers/md/Kconfig

1d35aae78ffe739bf46c2bf9dea7b51a4eebfbe0 - Merge tag 'kbuild-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild

Thu, 21 Mar 2024 22:41:00 +0100

Merge tag 'kbuild-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuildPull Kbuild updates from Masahiro Yamada: - Generate a list of built DTB files (arch/*/boot/dts/dtbs-list) - Use more threads when building Debian packages in parallel - Fix warnings shown during the RPM kernel package uninstallation - Change OBJECT_FILES_NON_STANDARD_*.o etc. to take a relative path to Makefile - Support GCC's -fmin-function-alignment flag - Fix a null pointer dereference bug in modpost - Add the DTB support to the RPM package - Various fixes and cleanups in Kconfig* tag 'kbuild-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild: (67 commits) kconfig: tests: test dependency after shuffling choices kconfig: tests: add a test for randconfig with dependent choices kconfig: tests: support KCONFIG_SEED for the randconfig runner kbuild: rpm-pkg: add dtb files in kernel rpm kconfig: remove unneeded menu_is_visible() call in conf_write_defconfig() kconfig: check prompt for choice while parsing kconfig: lxdialog: remove unused dialog colors kconfig: lxdialog: fix button color for blackbg theme modpost: fix null pointer dereference kbuild: remove GCC's default -Wpacked-bitfield-compat flag kbuild: unexport abs_srctree and abs_objtree kbuild: Move -Wenum-{compare-conditional,enum-conversion} into W=1 kconfig: remove named choice support kconfig: use linked list in get_symbol_str() to iterate over menus kconfig: link menus to a symbol kbuild: fix inconsistent indentation in top Makefile kbuild: Use -fmin-function-alignment when available alpha: merge two entries for CONFIG_ALPHA_GAMMA alpha: merge two entries for CONFIG_ALPHA_EV4 kbuild: change DTC_FLAGS_.o to take the path relative to $(obj) ... List of files: /linux/drivers/md/Kconfig

f36b1d3ba533d21b5b793623f05761b0297d114e - dm vdo: use a proper Makefile for dm-vdo

Sat, 27 Jan 2024 03:18:33 +0100

dm vdo: use a proper Makefile for dm-vdoRequires moving dm-vdo-target.c into drivers/md/dm-vdo/This change adds a proper drivers/md/dm-vdo/Makefile and eliminatesthe abnormal use of patsubst in drivers/md/Makefile -- which was thecause of at least one build failure that was reported by the upstreambuild bot.Also, split out VDO's drivers/md/dm-vdo/Kconfig and include it fromdrivers/md/KconfigSigned-off-by: Mike Snitzer Signed-off-by: Matthew Sakai List of files: /linux/drivers/md/Kconfig

f11aca85b0346fe7d04eca6eb8db2011398782e7 - dm vdo: enable configuration and building of dm-vdo

Fri, 17 Nov 2023 03:28:35 +0100

dm vdo: enable configuration and building of dm-vdodm-vdo targets are not supported for 32-bit configurations. A vdo targettypically requires 1 to 1.5 GB of memory at any given time, which is likelya large fraction of the addressable memory of a 32-bit system. At the sametime, the amount of addressable storage attached to a 32-bit system may notbe large enough for deduplication to provide much benefit. Because of theseconcerns, 32-bit platforms are deemed unlikely to benefit from using a vdotarget, so dm-vdo is targeted only at 64-bit platforms.Co-developed-by: J. corwin Coburn Signed-off-by: J. corwin Coburn Co-developed-by: John Wiele Signed-off-by: John Wiele Signed-off-by: Matthew Sakai Signed-off-by: Mike Snitzer List of files: /linux/drivers/md/Kconfig

cd14b01846612f3f3277e97bfbecba4c8cee5ce9 - treewide: replace or remove redundant def_bool in Kconfig files

Sun, 11 Feb 2024 13:48:08 +0100

treewide: replace or remove redundant def_bool in Kconfig files'def_bool X' is a shorthand for 'bool' plus 'default X'.'def_bool' is redundant where 'bool' is already present, so 'def_bool X'can be replaced with 'default X', or removed if X is 'n'.Signed-off-by: Masahiro Yamada List of files: /linux/drivers/md/Kconfig

01d550f0fcc06c7292f79a6f1453aac122d1d2c8 - Merge tag 'for-6.8/block-2024-01-08' of git://git.kernel.dk/linux

Thu, 11 Jan 2024 22:58:04 +0100

Merge tag 'for-6.8/block-2024-01-08' of git://git.kernel.dk/linuxPull block updates from Jens Axboe: "Pretty quiet round this time around. This contains: - NVMe updates via Keith: - nvme fabrics spec updates (Guixin, Max) - nvme target udpates (Guixin, Evan) - nvme attribute refactoring (Daniel) - nvme-fc numa fix (Keith) - MD updates via Song: - Fix/Cleanup RCU usage from conf->disks[i].rdev (Yu Kuai) - Fix raid5 hang issue (Junxiao Bi) - Add Yu Kuai as Reviewer of the md subsystem - Remove deprecated flavors (Song Liu) - raid1 read error check support (Li Nan) - Better handle events off-by-1 case (Alex Lyakas) - Efficiency improvements for passthrough (Kundan) - Support for mapping integrity data directly (Keith) - Zoned write fix (Damien) - rnbd fixes (Kees, Santosh, Supriti) - Default to a sane discard size granularity (Christoph) - Make the default max transfer size naming less confusing (Christoph) - Remove support for deprecated host aware zoned model (Christoph) - Misc fixes (me, Li, Matthew, Min, Ming, Randy, liyouhong, Daniel, Bart, Christoph)"* tag 'for-6.8/block-2024-01-08' of git://git.kernel.dk/linux: (78 commits) block: Treat sequential write preferred zone type as invalid block: remove disk_clear_zoned sd: remove the !ZBC && blk_queue_is_zoned case in sd_read_block_characteristics drivers/block/xen-blkback/common.h: Fix spelling typo in comment blk-cgroup: fix rcu lockdep warning in blkg_lookup() blk-cgroup: don't use removal safe list iterators block: floor the discard granularity to the physical block size mtd_blkdevs: use the default discard granularity bcache: use the default discard granularity zram: use the default discard granularity null_blk: use the default discard granularity nbd: use the default discard granularity ubd: use the default discard granularity block: default the discard granularity to sector size bcache: discard_granularity should not be smaller than a sector block: remove two comments in bio_split_discard block: rename and document BLK_DEF_MAX_SECTORS loop: don't abuse BLK_DEF_MAX_SECTORS aoe: don't abuse BLK_DEF_MAX_SECTORS null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS ... List of files: /linux/drivers/md/Kconfig