Changes in Makefile

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/Makefile

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/Makefile

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/Makefile

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/Makefile

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/Makefile

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/Makefile

231af470 - dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation

Mon, 27 Jun 2022 15:35:26 +0000

dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilationThe verity glue for LoadPin is only needed when CONFIG_SECURITY_LOADPIN_VERITYis set, use this option for conditional compilation instead of the combo ofCONFIG_DM_VERITY and CONFIG_SECURITY_LOADPIN.Signed-off-by: Matthias Kaehlcke Acked-by: Mike Snitzer Link: https://lore.kernel.org/lkml/20220627083512.v7.3.I5aca2dcc3b06de4bf53696cd21329dce8272b8aa@changeidSigned-off-by: Kees Cook List of files: /linux-6.15/drivers/md/Makefile

b6c1c574 - dm: Add verity helpers for LoadPin

Mon, 27 Jun 2022 15:35:24 +0000

dm: Add verity helpers for LoadPinLoadPin limits loading of kernel modules, firmware and certainother files to a 'pinned' file system (typically a read-onlyrootfs). To provide more flexibility LoadPin is being extendedto also allow loading these files from trusted dm-veritydevices. For that purpose LoadPin can be provided with a listof verity root digests that it should consider as trusted.Add a bunch of helpers to allow LoadPin to check whether a DMdevice is a trusted verity device. The new functions broadlyfall in two categories: those that need access to verityinternals (like the root digest), and the 'glue' betweenLoadPin and verity. The new file dm-verity-loadpin.c containsthe glue functions.Signed-off-by: Matthias Kaehlcke Acked-by: Mike Snitzer Link: https://lore.kernel.org/lkml/20220627083512.v7.1.I3e928575a23481121e73286874c4c2bdb403355d@changeidSigned-off-by: Kees Cook List of files: /linux-6.15/drivers/md/Makefile

61cbe788 - dm: add dm_bio_rewind() API to DM core

Fri, 24 Jun 2022 14:12:52 +0000

dm: add dm_bio_rewind() API to DM coreCommit 7759eb23fd98 ("block: remove bio_rewind_iter()") removeda similar API for the following reasons: ``` It is pointed that bio_rewind_iter() is one very bad API[1]: 1) bio size may not be restored after rewinding 2) it causes some bogus change, such as 5151842b9d8732 (block: reset bi_iter.bi_done after splitting bio) 3) rewinding really makes things complicated wrt. bio splitting 4) unnecessary updating of .bi_done in fast path [1] https://marc.info/?t=153549924200005&r=1&w=2 So this patch takes Kent's suggestion to restore one bio into its original state via saving bio iterator(struct bvec_iter) in bio_integrity_prep(), given now bio_rewind_iter() is only used by bio integrity code. ```However, saving off a copy of the 32 bytes bio->bi_iter in case rewindneeded isn't efficient because it bloats per-bio-data for what is anunlikely case. That suggestion also ignores the need to restorecrypto and integrity info.Add dm_bio_rewind() API for a specific use-case that is much more narrowthan the previous more generic rewind code that was reverted:1) most bios have a fixed end sector since bio split is done from front of the bio, if driver just records how many sectors between current bio's start sector and the original bio's end sector, the original position can be restored. Keeping the original bio's end sector fixed is a _hard_ requirement for this interface!2) if a bio's end sector won't change (usually bio_trim() isn't called, or in the case of DM it preserves original bio), user can restore the original position by storing sector offset from the current ->bi_iter.bi_sector to bio's end sector; together with saving bio size, only 8 bytes is needed to restore to original bio.3) DM's requeue use case: when BLK_STS_DM_REQUEUE happens, DM core needs to restore to an "original bio" which represents the current dm_io to be requeued (which may be a subset of the original bio). By storing the sector offset from the original bio's end sector and dm_io's size, dm_bio_rewind() can restore such original bio. See commit 7dd76d1feec7 ("dm: improve bio splitting and associated IO accounting") for more details on how DM does this. Leveraging this, allows DM core to shift the need for bio cloning from bio-split time (during IO submission) to the less likely BLK_STS_DM_REQUEUE handling (after IO completes with that error).4) Unlike the original rewind API, dm_bio_rewind() doesn't add .bi_done to bvec_iter and there is no effect on the fast path.Implement dm_bio_rewind() by factoring out clear helpers that it calls:dm_bio_integrity_rewind, dm_bio_crypt_rewind and dm_bio_rewind_iter.DM is able to ensure that dm_bio_rewind() is used safely but, giventhe constraint that the bio's end must never change, otherhypothetical future callers may not take the same care. So makedm_bio_rewind() and all supporting code local to DM to avoid risk ofhypothetical abuse. A "dm_" prefix was added to all functions to avoidany namespace collisions.Suggested-by: Jens Axboe Signed-off-by: Ming Lei Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

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/Makefile

91ccbbac - dm ima: measure data on table load

Tue, 13 Jul 2021 00:48:58 +0000

dm ima: measure data on table loadDM configures a block device with various target specific attributespassed to it as a table. DM loads the table, and calls each target’srespective constructors with the attributes as input parameters.Some of these attributes are critical to ensure the device meetscertain security bar. Thus, IMA should measure these attributes, toensure they are not tampered with, during the lifetime of the device.So that the external services can have high confidence in theconfiguration of the block-devices on a given system.Some devices may have large tables. And a given device may change itsstate (table-load, suspend, resume, rename, remove, table-clear etc.)many times. Measuring these attributes each time when the devicechanges its state will significantly increase the size of the IMA logs.Further, once configured, these attributes are not expected to changeunless a new table is loaded, or a device is removed and recreated.Therefore the clear-text of the attributes should only be measuredduring table load, and the hash of the active/inactive table should bemeasured for the remaining device state changes.Export IMA function ima_measure_critical_data() to allow measurementof DM device parameters, as well as target specific attributes, duringtable load. Compute the hash of the inactive table and store it formeasurements during future state change. If a load is called multipletimes, update the inactive table hash with the hash of the latestpopulated table. So that the correct inactive table hash is measuredwhen the device transitions to different states like resume, remove,rename, etc.Signed-off-by: Tushar Sugandhi Signed-off-by: Colin Ian King # leak fixSigned-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

7fc18728 - dm: move zone related code to dm-zone.c

Tue, 25 May 2021 21:24:56 +0000

dm: move zone related code to dm-zone.cMove core and table code used for zoned targets and conditionallydefined with #ifdef CONFIG_BLK_DEV_ZONED to the new file dm-zone.c.This file is conditionally compiled depending on CONFIG_BLK_DEV_ZONED.The small helper dm_set_zones_restrictions() is introduced toinitialize a mapped device request queue zone attributes indm_table_set_restrictions().Signed-off-by: Damien Le Moal Reviewed-by: Johannes Thumshirn Reviewed-by: Hannes Reinecke Reviewed-by: Himanshu Madhani Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

298fb372 - dm: rename multipath path selector source files to have "dm-ps" prefix

Tue, 10 Nov 2020 18:41:53 +0000

dm: rename multipath path selector source files to have "dm-ps" prefixAdditional prefix helps clarify that these source files implement pathselectors.Required updating Makefile to still build modules _without_ the"dm-ps" prefix to preserve dm-multipath's ability to autoload pathselector modules. While at it, cleaned up some DM whitespace inMakefile.Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

e4d2e82b - dm mpath: add IO affinity path selector

Fri, 23 Oct 2020 00:27:50 +0000

dm mpath: add IO affinity path selectorThis patch adds a path selector that selects paths based on a CPU topath mapping the user passes in and what CPU we are executing on. Theprimary user for this PS is where the app is optimized to use specificCPUs so other PSs undo the apps handy work, and the storage and it'stransport are not a bottlneck.For these io-affinity PS setups a path's transport/interconnectperf is not going to flucuate a lot and there is no major differencesbetween paths, so QL/HST smarts do not help and RR always messes upwhat the app is trying to do.On a system with 16 cores, where you have a job per CPU:fio --filename=/dev/dm-0 --direct=1 --rw=randrw --bs=4k \--ioengine=libaio --iodepth=128 --numjobs=16and a dm-multipath device setup where each CPU is mapped to one path:// When in mq mode I had to set dm_mq_nr_hw_queues=$NUM_PATHS.// Bio mode also showed similar results.0 16777216 multipath 0 0 1 1 io-affinity 0 16 1 8:16 1 8:32 2 8:64 48:48 8 8:80 10 8:96 20 8:112 40 8:128 80 8:144 100 8:160 200 8:176400 8:192 800 8:208 1000 8:224 2000 8:240 4000 65:0 8000we can see a IOPs increase of 25%.The percent increase depends on the device and interconnect. For aslower/medium speed path/device that can do around 180K IOPs a pathif you ran that fio command to it directly we saw a 25% increase likeabove. Slower path'd devices that could do around 90K per path showedmaybe around a 2 - 5% increase. If you use something like null_blk orscsi_debug which can multi-million IOPs and hack it up so each devicethey export shows up as a path then you see 50%+ increases.Signed-off-by: Mike Christie Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

4f5b246b - md: move the early init autodetect code to drivers/md/

Sun, 07 Jun 2020 14:18:59 +0000

md: move the early init autodetect code to drivers/md/Just like the NFS and CIFS root code this better lives with thedriver it is tightly integrated with.Signed-off-by: Christoph Hellwig Acked-by: Song Liu Acked-by: Linus Torvalds List of files: /linux-6.15/drivers/md/Makefile

2613eab1 - dm mpath: add Historical Service Time Path Selector

Thu, 30 Apr 2020 20:48:30 +0000

dm mpath: add Historical Service Time Path SelectorThis new selector keeps an exponential moving average of the servicetime for each path (losely defined as delta between start_io andend_io), and uses this along with the number of inflight requests toestimate future service time for a path. Since we don't have a proberto account for temporally slow paths, re-try "slow" paths every once ina while (num_paths * historical_service_time). To account for fast pathstransitioning to slow, if a path has not completed any request within(num_paths * historical_service_time), limit the number of outstandingrequests. To account for low volume situations where number ofinflight IOs would be zero, the last finish time of each path isfactored in.Signed-off-by: Khazhismel Kumykov Co-developed-by: Gabriel Krisman Bertazi Signed-off-by: Gabriel Krisman Bertazi Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

d3c7b35c - dm: add emulated block size target

Mon, 09 Mar 2020 22:26:38 +0000

dm: add emulated block size targetThis new target is similar to the linear target except that it emulatesa smaller logical block size on a device with a larger logical blocksize. Its main purpose is to emulate 512 byte sectors on 4K nativedisks (i.e. 512e).See Documentation/admin-guide/device-mapper/dm-ebs.rst for details.Reviewed-by: Damien Le Moal Signed-off-by: Heinz Mauelshagen Signed-off-by: Randy Dunlap [Kconfig fixes]Signed-off-by: Zheng Bin [static fixes]Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

7431b783 - dm: add clone target

Wed, 11 Sep 2019 14:36:40 +0000

dm: add clone targetAdd the dm-clone target, which allows cloning of arbitrary blockdevices.dm-clone produces a one-to-one copy of an existing, read-only sourcedevice into a writable destination device: It presents a virtual blockdevice which makes all data appear immediately, and redirects reads andwrites accordingly.The main use case of dm-clone is to clone a potentially remote,high-latency, read-only, archival-type block device into a writable,fast, primary-type device for fast, low-latency I/O. The cloned deviceis visible/mountable immediately and the copy of the source device tothe destination device happens in the background, in parallel with userI/O.When the cloning completes, the dm-clone table can be removed altogetherand be replaced, e.g., by a linear table, mapping directly to thedestination device.For further information and examples of how to use dm-clone, please readDocumentation/admin-guide/device-mapper/dm-clone.rstSuggested-by: Vangelis Koukis Co-developed-by: Ilias Tsitsimpis Signed-off-by: Ilias Tsitsimpis Signed-off-by: Nikos Tsironis Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

88cd3e6c - dm verity: add root hash pkcs#7 signature verification

Thu, 18 Jul 2019 00:46:15 +0000

dm verity: add root hash pkcs#7 signature verificationThe verification is to support cases where the root hash is not securedby Trusted Boot, UEFI Secureboot or similar technologies.One of the use cases for this is for dm-verity volumes mounted afterboot, the root hash provided during the creation of the dm-verity volumehas to be secure and thus in-kernel validation implemented here will beused before we trust the root hash and allow the block device to becreated.The signature being provided for verification must verify the root hashand must be trusted by the builtin keyring for verification to succeed.The hash is added as a key of type "user" and the description is passedto the kernel so it can look it up and use it for verification.Adds CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG which can be turned on if roothash verification is needed.Kernel commandline dm_verity module parameter 'require_signatures' willindicate whether to force root hash signature verification (for all dmverity volumes).Signed-off-by: Jaskaran Khurana Tested-and-Reviewed-by: Milan Broz Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile

e4f3fabd - dm: add dust target

Thu, 07 Mar 2019 20:42:39 +0000

dm: add dust targetAdd the dm-dust target, which simulates the behavior of bad sectorsat arbitrary locations, and the ability to enable the emulation ofthe read failures at an arbitrary time.This target behaves similarly to a linear target. At a given time,the user can send a message to the target to start failing readrequests on specific blocks. When the failure behavior is enabled,reads of blocks configured "bad" will fail with EIO.Writes of blocks configured "bad" will result in the following:1. Remove the block from the "bad block list".2. Successfully complete the write.After this point, the block will successfully contain the writtendata, and will service reads and writes normally. This emulates thebehavior of a "remapped sector" on a hard disk drive.dm-dust provides logging of which blocks have been added or removedto the "bad block list", as well as logging when a block has beenremoved from the bad block list. These messages can be usedalongside the messages from the driver using a dm-dust device toanalyze the driver's behavior when a read fails at a given time.(This logging can be reduced via a "quiet" mode, if desired.)NOTE: If the block size is larger than 512 bytes, only the first sectorof each "dust block" is detected. Placing a limiting layer above a dusttarget, to limit the minimum I/O size to the dust block size, willensure proper emulation of the given large block size.Signed-off-by: Bryan Gurney Co-developed-by: Joe Shimkus Co-developed-by: John Dorminy Co-developed-by: John Pittman Co-developed-by: Thomas Jaskiewicz Signed-off-by: Mike Snitzer List of files: /linux-6.15/drivers/md/Makefile