Changes in Kconfig

b261d222 - lib/crc: remove CONFIG_LIBCRC32C

Tue, 01 Apr 2025 22:16:00 +0000

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-6.15/drivers/md/Kconfig

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

Mon, 27 Jan 2025 22:15:33 +0000

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-6.15/drivers/md/Kconfig

127186cf - md: reintroduce md-linear

Thu, 02 Jan 2025 11:28:41 +0000

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-6.15/drivers/md/Kconfig

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

Tue, 02 Jul 2024 16:16:57 +0000

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-6.15/drivers/md/Kconfig

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

Sat, 27 Jan 2024 02:18:33 +0000

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-6.15/drivers/md/Kconfig

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

Fri, 17 Nov 2023 02:28:35 +0000

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-6.15/drivers/md/Kconfig

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

Sun, 11 Feb 2024 12:48:08 +0000

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-6.15/drivers/md/Kconfig

415c7451 - md: Remove deprecated CONFIG_MD_FAULTY

Thu, 14 Dec 2023 22:21:07 +0000

md: Remove deprecated CONFIG_MD_FAULTYmd-faulty has been marked as deprecated for 2.5 years. Remove it.Cc: Christoph Hellwig Cc: Jens Axboe Cc: Neil Brown Cc: Guoqing Jiang Cc: Mateusz Grzonka Cc: Jes Sorensen Signed-off-by: Song Liu Reviewed-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Link: https://lore.kernel.org/r/20231214222107.2016042-4-song@kernel.org List of files: /linux-6.15/drivers/md/Kconfig

d8730f0c - md: Remove deprecated CONFIG_MD_MULTIPATH

Thu, 14 Dec 2023 22:21:06 +0000

md: Remove deprecated CONFIG_MD_MULTIPATHmd-multipath has been marked as deprecated for 2.5 years. Remove it.Cc: Christoph Hellwig Cc: Jens Axboe Cc: Neil Brown Cc: Guoqing Jiang Cc: Mateusz Grzonka Cc: Jes Sorensen Signed-off-by: Song Liu Reviewed-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Link: https://lore.kernel.org/r/20231214222107.2016042-3-song@kernel.org List of files: /linux-6.15/drivers/md/Kconfig

849d18e2 - md: Remove deprecated CONFIG_MD_LINEAR

Thu, 14 Dec 2023 22:21:05 +0000

md: Remove deprecated CONFIG_MD_LINEARmd-linear has been marked as deprecated for 2.5 years. Remove it.Cc: Christoph Hellwig Cc: Jens Axboe Cc: Neil Brown Cc: Guoqing Jiang Cc: Mateusz Grzonka Cc: Jes Sorensen Signed-off-by: Song Liu Reviewed-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Link: https://lore.kernel.org/r/20231214222107.2016042-2-song@kernel.org List of files: /linux-6.15/drivers/md/Kconfig

6849302f - dm audit: fix Kconfig so DM_AUDIT depends on BLK_DEV_DM

Wed, 13 Dec 2023 19:46:19 +0000

dm audit: fix Kconfig so DM_AUDIT depends on BLK_DEV_DMSigned-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Kconfig

925c86a1 - fs: add CONFIG_BUFFER_HEAD

Tue, 01 Aug 2023 17:22:01 +0000

fs: add CONFIG_BUFFER_HEADAdd a new config option that controls building the buffer_head code, andselect it from all file systems and stacking drivers that need it.For the block device nodes and alternative iomap based buffered I/O pathis provided when buffer_head support is not enabled, and iomap needs aa small tweak to define the IOMAP_F_BUFFER_HEAD flag to 0 to not callinto the buffer_head code when it doesn't exist.Otherwise this is just Kconfig and ifdef changes.Signed-off-by: Christoph Hellwig Reviewed-by: Luis Chamberlain Reviewed-by: Johannes Thumshirn Link: https://lore.kernel.org/r/20230801172201.1923299-7-hch@lst.deSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/md/Kconfig

0ae1c9d3 - md: deprecate bitmap file support

Thu, 15 Jun 2023 06:48:40 +0000

md: deprecate bitmap file supportThe support for bitmaps on files is a very bad idea abusing various kernelAPIs, and fundamentally requires the file to not be on the actual arraywithout a way to check that this is actually the case. Add a deprecationwarning to see if we might be able to eventually drop it.Signed-off-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Reviewed-by: Himanshu Madhani Signed-off-by: Song Liu Link: https://lore.kernel.org/r/20230615064840.629492-12-hch@lst.de List of files: /linux-6.15/drivers/md/Kconfig

a34d4ef8 - md: make bitmap file support optional

Thu, 15 Jun 2023 06:48:39 +0000

md: make bitmap file support optionalThe support for write intent bitmaps in files on an external files in mdis a hot mess that abuses ->bmap to map file offsets into physical deviceobjects, and also abuses buffer_heads in a creative way.Make this code optional so that MD can be built into future kernelswithout buffer_head support, and so that we can eventually deprecate it.Note this does not affect the internal bitmap support, which has none ofthe problems.Signed-off-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Reviewed-by: Himanshu Madhani Signed-off-by: Song Liu Link: https://lore.kernel.org/r/20230615064840.629492-11-hch@lst.de List of files: /linux-6.15/drivers/md/Kconfig

6c0f5898 - md: select BLOCK_LEGACY_AUTOLOAD

Mon, 13 Mar 2023 20:29:17 +0000

md: select BLOCK_LEGACY_AUTOLOADWhen BLOCK_LEGACY_AUTOLOAD is not enable, mdadm is not able toactivate new arrays unless "CREATE names=yes" appears inmdadm.confAs this is a regression we need to always enable BLOCK_LEGACY_AUTOLOADfor when MD is selected - at least until mdadm is updated and theupdates widely available.Cc: stable@vger.kernel.org # v5.18+Fixes: fbdee71bb5d8 ("block: deprecate autoloading based on dev_t")Signed-off-by: NeilBrown Signed-off-by: Song Liu List of files: /linux-6.15/drivers/md/Kconfig

9276cf8b - drivers/md: Remove "select SRCU"

Wed, 23 Nov 2022 01:24:14 +0000

drivers/md: Remove "select SRCU"Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it. Therefore, remove the "select SRCU"Kconfig statements.Signed-off-by: Paul E. McKenney Cc: Song Liu Cc: Alasdair Kergon Cc: Mike Snitzer Cc: Cc: Acked-by: Mike Snitzer Reviewed-by: John Ogness List of files: /linux-6.15/drivers/md/Kconfig

248c7933 - blk-mq: make the blk-mq stacking code optional

Tue, 15 Feb 2022 10:05:36 +0000

blk-mq: make the blk-mq stacking code optionalThe code to stack blk-mq drivers is only used by dm-multipath, andwill preferably stay that way. Make it optional and only selectedby device mapper, so that the buildbots more easily catch abuseslike the one that slipped in in the ufs driver in the last mergedwindow. Another positive side effects is that kernel builds withoutdevice mapper shrink a little bit as well.Signed-off-by: Christoph Hellwig Reviewed-by: Mike Snitzer Link: https://lore.kernel.org/r/20220215100540.3892965-2-hch@lst.deSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/md/Kconfig

82bb8599 - dm integrity: log audit events for dm-integrity target

Sat, 04 Sep 2021 09:59:29 +0000

dm integrity: log audit events for dm-integrity targetdm-integrity signals integrity violations by returning I/O errorsto user space. To identify integrity violations by a controllinginstance, the kernel audit subsystem can be used to emit auditevents to user space. We use the new dm-audit submodule allowingto emit audit events on relevant I/O errors.The construction and destruction of integrity device mappings arealso relevant for auditing a system. Thus, those events are alsologged as audit events.Signed-off-by: Michael Weiß Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Kconfig

2cc1ae48 - dm: introduce audit event module for device mapper

Sat, 04 Sep 2021 09:59:28 +0000

dm: introduce audit event module for device mapperTo be able to send auditing events to user space, we introduce ageneric dm-audit module. It provides helper functions to emit auditevents through the kernel audit subsystem. We claim theAUDIT_DM_CTRL type=1336 and AUDIT_DM_EVENT type=1337 out of theaudit event messages range in the corresponding userspace api in'include/uapi/linux/audit.h' for those events.AUDIT_DM_CTRL is used to provide information about creation anddestruction of device mapper targets which are triggered by user spaceadmin control actions.AUDIT_DM_EVENT is used to provide information about actual errorsduring operation of the mapped device, showing e.g. integrityviolations in audit log.Following commits to device mapper targets actually will make use ofthis to emit those events in relevant cases.The audit logs look like this if executing the following simple test: # dd if=/dev/zero of=test.img bs=1M count=1024 # losetup -f test.img # integritysetup -vD format --integrity sha256 -t 32 /dev/loop0 # integritysetup open -D /dev/loop0 --integrity sha256 integritytest # integritysetup status integritytest # integritysetup close integritytest # integritysetup open -D /dev/loop0 --integrity sha256 integritytest # integritysetup status integritytest # dd if=/dev/urandom of=/dev/loop0 bs=512 count=1 seek=100000 # dd if=/dev/mapper/integritytest of=/dev/null-------------------------audit.log from auditdtype=UNKNOWN[1336] msg=audit(1630425039.363:184): module=integrityop=ctr ppid=3807 pid=3819 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425039.471:185): module=integrityop=dtr ppid=3807 pid=3819 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425039.611:186): module=integrityop=ctr ppid=3807 pid=3819 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425054.475:187): module=integrityop=dtr ppid=3807 pid=3819 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425073.171:191): module=integrityop=ctr ppid=3807 pid=3883 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425087.239:192): module=integrityop=dtr ppid=3807 pid=3902 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1336] msg=audit(1630425093.755:193): module=integrityop=ctr ppid=3807 pid=3906 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0egid=0 sgid=0 fsgid=0 tty=pts2 ses=3 comm="integritysetup"exe="/sbin/integritysetup" subj==unconfined dev=254:3error_msg='success' res=1type=UNKNOWN[1337] msg=audit(1630425112.119:194): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:195): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:196): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:197): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:198): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:199): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:200): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:201): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:202): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0type=UNKNOWN[1337] msg=audit(1630425112.119:203): module=integrityop=integrity-checksum dev=254:3 sector=77480 res=0Signed-off-by: Michael Weiß Signed-off-by: Paul Moore # fix audit.h numberingSigned-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Kconfig

1c277e50 - dm: make EBS depend on !HIGHMEM

Wed, 04 Aug 2021 09:56:22 +0000

dm: make EBS depend on !HIGHMEM__ebs_rw_bvec use page_address on the submitted bios data, and thuscan't deal with highmem. Disable the target on highmem configs.Signed-off-by: Christoph Hellwig Link: https://lore.kernel.org/r/20210804095634.460779-4-hch@lst.deSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/md/Kconfig