Linux Device-Mapper Development

• Date Index

• [RFC PATCH v2 11/12] documentation: Add IPE Documentation, (continued)
  • [RFC PATCH v2 11/12] documentation: Add IPE Documentation, deven . desai
    • Re: [RFC PATCH v2 11/12] documentation: Add IPE Documentation, Jonathan Corbet
      • Re: [RFC PATCH v2 11/12] documentation: Add IPE Documentation, Deven Bowers
  • [RFC PATCH v2 03/12] security: add ipe lsm policy parser and policy loading, deven . desai
    • Re: [RFC PATCH v2 03/12] security: add ipe lsm policy parser and policy loading, Jann Horn
      • Re: [RFC PATCH v2 03/12] security: add ipe lsm policy parser and policy loading, Deven Bowers
  • [RFC PATCH v2 01/12] scripts: add ipe tooling to generate boot policy, deven . desai
  • [RFC PATCH v2 10/12] ipe: add property for dmverity roothash, deven . desai
  • [RFC PATCH v2 02/12] security: add ipe lsm evaluation loop and audit system, deven . desai
    • Re: [RFC PATCH v2 02/12] security: add ipe lsm evaluation loop and audit system, Jann Horn
      • Re: [RFC PATCH v2 02/12] security: add ipe lsm evaluation loop and audit system, Deven Bowers
  • [RFC PATCH v2 09/12] dm-verity: add bdev_setsecurity hook for root-hash, deven . desai
  • [RFC PATCH v2 08/12] ipe: add property for signed dmverity volumes, deven . desai
  • [RFC PATCH v2 07/12] dm-verity: add bdev_setsecurity hook for dm-verity signature, deven . desai
  • [RFC PATCH v2 05/12] fs: add security blob and hooks for block_device, deven . desai
  • [RFC PATCH v2 04/12] ipe: add property for trust of boot volume, deven . desai
  • Re: [RFC PATCH v2 00/12] Integrity Policy Enforcement LSM (IPE), Nayna
    • Re: [RFC PATCH v2 00/12] Integrity Policy Enforcement LSM (IPE), Deven Bowers
• [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE), deven . desai
  • [RESEND PATCH 01/11] scripts: add ipe tooling to generate boot policy, deven . desai
  • [RESEND PATCH 11/11] cleanup: uapi/linux/audit.h, deven . desai
  • [RESEND PATCH 04/11] fs: add security blob and hooks for block_device, deven . desai
  • [RESEND PATCH 09/11] ipe: add property for dmverity roothash, deven . desai
  • [RESEND PATCH 06/11] dm-verity: add bdev_setsecurity hook for dm-verity signature, deven . desai
  • [RESEND PATCH 10/11] documentation: Add IPE Documentation, deven . desai
  • [RESEND PATCH 05/11] dm-verity: move signature check after tree validation, deven . desai
  • Re: [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE), Jann Horn
    • Re: [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE), Deven Bowers
      • Re: [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE), Sasha Levin
  • [RESEND PATCH 08/11] dm-verity: add bdev_setsecurity hook for root-hash, deven . desai
  • [RESEND PATCH 02/11] security: add ipe lsm, deven . desai
  • [RESEND PATCH 07/11] ipe: add property for signed dmverity volumes, deven . desai
  • [RESEND PATCH 03/11] ipe: add property for trust of boot volume, deven . desai
  • Re: [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE), Deven Bowers
• [PATCHv2 00/11] dm-zoned: metadata version 2, Hannes Reinecke
  • [PATCH 01/11] dm-zoned: store zone id within the zone structure, Hannes Reinecke
    • Re: [PATCH 01/11] dm-zoned: store zone id within the zone structure, Damien Le Moal
      • Re: [PATCH 01/11] dm-zoned: store zone id within the zone structure, Hannes Reinecke
  • [PATCH 02/11] dm-zoned: use array for superblock zones, Hannes Reinecke
    • Re: [PATCH 02/11] dm-zoned: use array for superblock zones, Damien Le Moal
  • [PATCH 08/11] dm-zoned: use dmz_zone_to_dev() when handling metadata I/O, Hannes Reinecke
    • Re: [PATCH 08/11] dm-zoned: use dmz_zone_to_dev() when handling metadata I/O, Damien Le Moal
  • [PATCH 06/11] dm-zoned: remove 'dev' argument from reclaim, Hannes Reinecke
    • Re: [PATCH 06/11] dm-zoned: remove 'dev' argument from reclaim, Damien Le Moal
      • Re: [PATCH 06/11] dm-zoned: remove 'dev' argument from reclaim, Hannes Reinecke
  • [PATCH 03/11] dm-zoned: store device in struct dmz_sb, Hannes Reinecke
    • Re: [PATCH 03/11] dm-zoned: store device in struct dmz_sb, Damien Le Moal
  • [PATCH 09/11] dm-zoned: add metadata logging functions, Hannes Reinecke
    • Re: [PATCH 09/11] dm-zoned: add metadata logging functions, Damien Le Moal
  • [PATCH 05/11] dm-zoned: introduce dmz_metadata_label() to format device name, Hannes Reinecke
    • Re: [PATCH 05/11] dm-zoned: introduce dmz_metadata_label() to format device name, Damien Le Moal
  • [PATCH 04/11] dm-zoned: move fields from struct dmz_dev to dmz_metadata, Hannes Reinecke
    • Re: [PATCH 04/11] dm-zoned: move fields from struct dmz_dev to dmz_metadata, Damien Le Moal
  • [PATCH 10/11] dm-zoned: ignore metadata zone in dmz_alloc_zone(), Hannes Reinecke
    • Re: [PATCH 10/11] dm-zoned: ignore metadata zone in dmz_alloc_zone(), Damien Le Moal
  • [PATCH 11/11] dm-zoned: metadata version 2, Hannes Reinecke
    • Re: [PATCH 11/11] dm-zoned: metadata version 2, Damien Le Moal
      • Re: [PATCH 11/11] dm-zoned: metadata version 2, Hannes Reinecke
  • [PATCH 07/11] dm-zoned: use device as argument for bio handler functions, Hannes Reinecke
    • Re: [PATCH 07/11] dm-zoned: use device as argument for bio handler functions, Damien Le Moal
      • Re: [PATCH 07/11] dm-zoned: use device as argument for bio handler functions, Hannes Reinecke
• Unused functions in dm-thin-metadata, Drew Hastings
• [PATCH] dm-integrity: fix logic bug in integrity tag testing, Mikulas Patocka
• [git pull] device mapper fixes for 5.7, Mike Snitzer
  • [git pull v2] device mapper fixes for 5.7, Mike Snitzer
    • Re: [git pull v2] device mapper fixes for 5.7, pr-tracker-bot
  • Re: [git pull] device mapper fixes for 5.7, pr-tracker-bot
• [PATCH v2 0/2] multipath-tools: fixes for kpartx.rules and skip_kpartx, mwilck
  • [PATCH v2 1/2] kpartx.rules: honor DM_UDEV_DISABLE_OTHER_RULES_FLAG, mwilck
    • Re: [PATCH v2 1/2] kpartx.rules: honor DM_UDEV_DISABLE_OTHER_RULES_FLAG, Benjamin Marzinski
  • [PATCH v2 2/2] kpartx.rules: check for skip_kpartx on synthetic uevents, mwilck
    • Re: [PATCH v2 2/2] kpartx.rules: check for skip_kpartx on synthetic uevents, Benjamin Marzinski
• [RFC PATCH v2 0/3] multipath: new path validation library, Benjamin Marzinski
  • [RFC PATCH v2 1/3] libmultipath: make libmp_dm_init optional, Benjamin Marzinski
  • [RFC PATCH v2 2/3] libmultipath: make sysfs_is_multipathed able to return wwid, Benjamin Marzinski
    • Re: [RFC PATCH v2 2/3] libmultipath: make sysfs_is_multipathed able to return wwid, Martin Wilck
  • [RFC PATCH v2 3/3] multipath: add libmpathvalid library, Benjamin Marzinski
    • Re: [RFC PATCH v2 3/3] multipath: add libmpathvalid library, Martin Wilck
      • Re: [RFC PATCH v2 3/3] multipath: add libmpathvalid library, Benjamin Marzinski
  • Re: [RFC PATCH v2 0/3] multipath: new path validation library, Martin Wilck
    • Re: [RFC PATCH v2 0/3] multipath: new path validation library, Benjamin Marzinski
• [PATCH] kpartx.rules: check for skip_kpartx if DM_ACTIVATION is unset, mwilck
• [git pull] device mapper changes for 5.7, Mike Snitzer
  • Re: [git pull] device mapper changes for 5.7, pr-tracker-bot
• [RFC Patch 0/3] multipath: new path validation library, Benjamin Marzinski
  • [RFC Patch 1/3] libmultipath: make libmp_dm_init optional, Benjamin Marzinski
    • Re: [RFC Patch 1/3] libmultipath: make libmp_dm_init optional, Martin Wilck
  • [RFC Patch 2/3] libmultipath: make sysfs_is_multipathed able to return wwid, Benjamin Marzinski
    • Re: [RFC Patch 2/3] libmultipath: make sysfs_is_multipathed able to return wwid, Martin Wilck
      • Re: [RFC Patch 2/3] libmultipath: make sysfs_is_multipathed able to return wwid, Benjamin Marzinski
  • [RFC Patch 3/3] multipath: add libmpathvalid library, Benjamin Marzinski
    • Re: [RFC Patch 3/3] multipath: add libmpathvalid library, Martin Wilck
      • Re: [RFC Patch 3/3] multipath: add libmpathvalid library, Benjamin Marzinski
        • Re: [RFC Patch 3/3] multipath: add libmpathvalid library, Martin Wilck
          • Re: [RFC Patch 3/3] multipath: add libmpathvalid library, Benjamin Marzinski
• [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
  • [PATCH v2] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
    • Re: [PATCH v2] memcpy_flushcache: use cache flusing for larger lengths, Elliott, Robert (Servers)
      • Re: [PATCH v2] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
        • Re: [PATCH v2] memcpy_flushcache: use cache flusing for larger lengths, Dan Williams
          • Re: [PATCH v2] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
  • <Possible follow-ups>
  • [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
    • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Dan Williams
      • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
        • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Dan Williams
          • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
            • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
              • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Dan Williams
                • [PATCH] x86: introduce memcpy_flushcache_clflushopt, Mikulas Patocka
                  • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, Dan Williams
                    • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, Thomas Gleixner
                      • [PATCH v2] x86: introduce memcpy_flushcache_single, Mikulas Patocka
                        • Re: [PATCH v2] x86: introduce memcpy_flushcache_single, Dan Williams
                  • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, David Laight
                    • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, Mikulas Patocka
                      • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, David Laight
                        • Re: [PATCH] x86: introduce memcpy_flushcache_clflushopt, Dan Williams
    • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Andy Lutomirski
      • Re: [PATCH] memcpy_flushcache: use cache flusing for larger lengths, Mikulas Patocka
• Optane nvdimm performance, Mikulas Patocka
  • Re: Optane nvdimm performance, Bruggeman, Otto (external - Partner)
    • Re: Optane nvdimm performance, Bruggeman, Otto (external - Partner)
• [PATCH] md: add missing mddev_unlock, Dinghao Liu
• [PATCH 0/4] dm clone: Fix discard handling and overflow bugs which could cause data corruption, Nikos Tsironis
  • [PATCH 3/4] dm clone: Add missing casts to prevent overflows and data corruption, Nikos Tsironis
  • [PATCH 2/4] dm clone: Add overflow check for number of regions, Nikos Tsironis
  • [PATCH 4/4] dm clone metadata: Fix return type of dm_clone_nr_of_hydrated_regions(), Nikos Tsironis
  • [PATCH 1/4] dm clone: Fix handling of partial region discards, Nikos Tsironis
• [PATCH] dm-writecache: add cond_resched, Mikulas Patocka
• [PATCH RFC 0/4] dm-zoned: Metadata V2, Hannes Reinecke
  • [PATCH 2/4] dm-zoned: use array for superblock zones, Hannes Reinecke
    • Re: [PATCH 2/4] dm-zoned: use array for superblock zones, Damien Le Moal
    • Re: [PATCH 2/4] dm-zoned: use array for superblock zones, Bob Liu
  • [PATCH 4/4] dm-zoned: allow for device size smaller than the capacity, Hannes Reinecke
    • Re: [PATCH 4/4] dm-zoned: allow for device size smaller than the capacity, Damien Le Moal
      • Re: [PATCH 4/4] dm-zoned: allow for device size smaller than the capacity, Hannes Reinecke
        • Re: [PATCH 4/4] dm-zoned: allow for device size smaller than the capacity, Damien Le Moal
  • [PATCH 3/4] dm-zoned: V2 metadata handling, Hannes Reinecke
    • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, Damien Le Moal
    • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, Bob Liu
      • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, John Dorminy
        • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, Hannes Reinecke
          • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, John Dorminy
            • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, John Dorminy
              • Re: [PATCH 3/4] dm-zoned: V2 metadata handling, Damien Le Moal
  • [PATCH 1/4] dm-zoned: store zone id within the zone structure, Hannes Reinecke
    • Re: [PATCH 1/4] dm-zoned: store zone id within the zone structure, Damien Le Moal
      • Re: [PATCH 1/4] dm-zoned: store zone id within the zone structure, Hannes Reinecke
• [PATCH] dm-zoned: add 'status' and 'message' callbacks, Hannes Reinecke
  • Re: [PATCH] dm-zoned: add 'status' and 'message' callbacks, Damien Le Moal
  • Re: dm-zoned: add 'status' and 'message' callbacks, Mike Snitzer
• storage-logger: Recording changes to the udev database, Alasdair G Kergon
  • Re: [linux-lvm] storage-logger: Recording changes to the udev database, Brian McCullough
  • Re: [linux-lvm] storage-logger: Recording changes to the udev database, Brian McCullough
    • Re: [linux-lvm] storage-logger: Recording changes to the udev database, Alasdair G Kergon
      • Re: [linux-lvm] storage-logger: Recording changes to the udev database, Brian McCullough
• [PATCH v2 1/3] libmultipath: assign variable to make gcc happy, Benjamin Marzinski
  • [PATCH v2 2/3] libmutipath: don't close fd on dm_lib_release, Benjamin Marzinski
    • Re: [PATCH v2 2/3] libmutipath: don't close fd on dm_lib_release, Martin Wilck
  • [PATCH v2 3/3] libmultipath: allow force reload with no active paths, Benjamin Marzinski
• [PATCH resend] dm zoned: remove duplicated nr_rnd_zones increasement, Bob Liu
  • Re: [PATCH resend] dm zoned: remove duplicated nr_rnd_zones increasement, Sasha Levin
    • Re: [PATCH resend] dm zoned: remove duplicated nr_rnd_zones increasement, Damien Le Moal
• [RFC PATCH v2 0/3] dm zoned: extend the way of exposing zoned block device, Bob Liu
  • Re: [RFC PATCH v2 0/3] dm zoned: extend the way of exposing zoned block device, Hannes Reinecke
    • Re: [RFC PATCH v2 0/3] dm zoned: extend the way of exposing zoned block device, Bob Liu
  • [RFC PATCH v2 2/3] dm zoned: introduce regular device to dm-zoned-target, Bob Liu
    • Re: [RFC PATCH v2 2/3] dm zoned: introduce regular device to dm-zoned-target, Damien Le Moal
  • [RFC PATCH v2 1/3] dm zoned: rename dev name to zoned_dev, Bob Liu
    • Re: [RFC PATCH v2 1/3] dm zoned: rename dev name to zoned_dev, Damien Le Moal
      • Re: [RFC PATCH v2 1/3] dm zoned: rename dev name to zoned_dev, Bob Liu
  • [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Bob Liu
    • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Damien Le Moal
      • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Hannes Reinecke
        • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Damien Le Moal
          • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Hannes Reinecke
            • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Damien Le Moal
              • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Hannes Reinecke
                • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Damien Le Moal
        • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Bob Liu
          • Re: [RFC PATCH v2 3/3] dm zoned: add regular device info to metadata, Hannes Reinecke
• [PATCH 1/3] libmultipath: assign variable to make gcc happy, Benjamin Marzinski
  • [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Benjamin Marzinski
    • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Martin Wilck
      • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Benjamin Marzinski
        • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Benjamin Marzinski
          • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Martin Wilck
          • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Martin Wilck
            • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Benjamin Marzinski
              • Re: [PATCH 2/3] libmutipath: don't close fd on dm_lib_release, Martin Wilck
  • [PATCH 3/3] libmultipath: allow force reload with no active paths, Benjamin Marzinski
    • Re: [PATCH 3/3] libmultipath: allow force reload with no active paths, Martin Wilck
  • Re: [PATCH 1/3] libmultipath: assign variable to make gcc happy, Martin Wilck
• [PATCH RFC 0/2] dm-zoned: add cache device, Hannes Reinecke
  • [PATCH 1/2] dm-zoned: cache device for zones, Hannes Reinecke
    • Re: [PATCH 1/2] dm-zoned: cache device for zones, Damien Le Moal
      • Re: [PATCH 1/2] dm-zoned: cache device for zones, Bob Liu
      • Re: [PATCH 1/2] dm-zoned: cache device for zones, Hannes Reinecke
        • Re: [PATCH 1/2] dm-zoned: cache device for zones, Damien Le Moal
  • [PATCH 2/2] dm-zoned: add 'status' and 'message' callbacks, Hannes Reinecke
    • Re: [PATCH 2/2] dm-zoned: add 'status' and 'message' callbacks, Damien Le Moal
      • Re: [PATCH 2/2] dm-zoned: add 'status' and 'message' callbacks, Mike Snitzer
        • Re: [PATCH 2/2] dm-zoned: add 'status' and 'message' callbacks, Damien Le Moal
  • Re: [PATCH RFC 0/2] dm-zoned: add cache device, Mike Snitzer
    • Re: [PATCH RFC 0/2] dm-zoned: add cache device, Hannes Reinecke
      • Re: [PATCH RFC 0/2] dm-zoned: add cache device, Mike Snitzer
        • Re: [PATCH RFC 0/2] dm-zoned: add cache device, Hannes Reinecke
          • Re: [PATCH RFC 0/2] dm-zoned: add cache device, Mike Snitzer
• multipathd: fix check_path could not resume path state, wangjufeng
  • Re: multipathd: fix check_path could not resume path state, Martin Wilck
• [PATCH] dm zoned: remove duplicated nr_rnd_zones increasement, Bob Liu
  • Re: [PATCH] dm zoned: remove duplicated nr_rnd_zones increasement, Damien Le Moal
• [PATCH 7/7] dm integrity: improve discard in journal mode, Mikulas Patocka
• [PATCH 5/7] dm-integrity: change the size of the device, Mikulas Patocka
• [PATCH 6/7] dm-integrity: support discard, Mikulas Patocka
• [PATCH 2/7] dm-integrity: remove sector type casts, Mikulas Patocka
• [PATCH 3/7] dm-integrity: dont replay journal data past the end of the device, Mikulas Patocka
• [PATCH 0/7] dm-integrity patches, Mikulas Patocka
  • Re: [PATCH 0/7] dm-integrity patches, Mike Snitzer
    • Re: [PATCH 0/7] dm-integrity patches, Mikulas Patocka
• [PATCH 4/7] dm-integrity: introduce get_provided_data_sectors, Mikulas Patocka
• [PATCH 1/7] dm-integrity: fix a crash with unusually large tag size, Mikulas Patocka
• [PATCH] dm-integrity: fix a crash with unusually large, Mikulas Patocka
• Re: [PATCH] dm verity fec: Fix memory leak in verity_fec_ctr, Sami Tolvanen
  • Re: [PATCH] dm verity fec: Fix memory leak in verity_fec_ctr, James Bottomley
• [PATCH] dm verity fec: Fix memory leak in verity_fec_ctr, Shetty, Harshini X (EXT-Sony Mobile)
  • Re: [PATCH] dm verity fec: Fix memory leak in verity_fec_ctr, Heinz Mauelshagen
    • Re: dm verity fec: Fix memory leak in verity_fec_ctr, Mike Snitzer
      • Re: dm verity fec: Fix memory leak in verity_fec_ctr, Mike Snitzer
• Regression due to commit dbaf971c9cdf10843071a60dcafc1aaab3162354 ?, Jean-François Remy
• [PATCH AUTOSEL 4.19 13/20] dm integrity: use dm_bio_record and dm_bio_restore, Sasha Levin
• [PATCH AUTOSEL 5.4 23/35] dm integrity: use dm_bio_record and dm_bio_restore, Sasha Levin
• [PATCH AUTOSEL 4.19 12/20] dm bio record: save/restore bi_end_io and bi_integrity, Sasha Levin
• [PATCH AUTOSEL 4.14 11/15] dm bio record: save/restore bi_end_io and bi_integrity, Sasha Levin
• [PATCH AUTOSEL 5.5 27/41] dm integrity: use dm_bio_record and dm_bio_restore, Sasha Levin
• [PATCH AUTOSEL 5.5 26/41] dm bio record: save/restore bi_end_io and bi_integrity, Sasha Levin
• [PATCH AUTOSEL 5.4 22/35] dm bio record: save/restore bi_end_io and bi_integrity, Sasha Levin
• [PATCH v2 0/4] [PATCH 0/4] libmpathpersist allocation size fixes, mwilck
  • [PATCH v2 1/4] libmpathpersist: limit PRIN allocation length to 8192 bytes, mwilck
  • [PATCH v2 2/4] libmpathpersist: format_transportids(): avoid PROUT overflow, mwilck
    • Re: [PATCH v2 2/4] libmpathpersist: format_transportids(): avoid PROUT overflow, Benjamin Marzinski
  • [PATCH v2 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, mwilck
    • Re: [PATCH v2 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, Benjamin Marzinski
  • [PATCH v2 3/4] libmpathpersist: mpath_format_readfullstatus(): use real buffer size, mwilck
• [PATCH -next 000/491] treewide: use fallthrough;, Joe Perches
• probable lvm thin_pool exhaustion, maiski
• Fix for dm-thin pool resizing, Drew Hastings
• [PATCH v4] dm ebs: new block size emulating target, heinzm
  • Re: [PATCH v4] dm ebs: new block size emulating target, Damien Le Moal
    • Re: [PATCH v4] dm ebs: new block size emulating target, Heinz Mauelshagen
      • Re: [PATCH v4] dm ebs: new block size emulating target, Mike Snitzer
• [PATCH 0/4] libmpathpersist allocation size fixes, mwilck
  • [PATCH 3/4] libmpathpersist: mpath_format_readfullstatus(): use real buffer size, mwilck
    • Re: [PATCH 3/4] libmpathpersist: mpath_format_readfullstatus(): use real buffer size, Benjamin Marzinski
  • [PATCH 1/4] libmpathpersist: limit PRIN allocation length to 8192 bytes, mwilck
    • Re: [PATCH 1/4] libmpathpersist: limit PRIN allocation length to 8192 bytes, Benjamin Marzinski
  • [PATCH 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, mwilck
    • Re: [PATCH 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, Benjamin Marzinski
      • Re: [PATCH 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, Martin Wilck
        • Re: [PATCH 4/4] libmpathpersist: ABI change: limit data-in/out size to 8192 bytes, Martin Wilck
  • [PATCH 2/4] libmpathpersist: format_transportids(): avoid PROUT overflow, mwilck
    • Re: [PATCH 2/4] libmpathpersist: format_transportids(): avoid PROUT overflow, Benjamin Marzinski
      • Re: [PATCH 2/4] libmpathpersist: format_transportids(): avoid PROUT overflow, Martin Wilck
• [PATCH] iscsi: do not wait for IOs in dm shrinker, Gabriel Krisman Bertazi
  • Re: [PATCH] iscsi: do not wait for IOs in dm shrinker, Mikulas Patocka
  • Re: [PATCH] iscsi: do not wait for IOs in dm shrinker, Christoph Hellwig
• [git pull] device mapper fixes for 5.6-rc5, Mike Snitzer
  • Re: [git pull] device mapper fixes for 5.6-rc5, Linus Torvalds
    • Re: [git pull] device mapper fixes for 5.6-rc5, Mike Snitzer
      • Re: [git pull] device mapper fixes for 5.6-rc5, Linus Torvalds
        • Re: [git pull] device mapper fixes for 5.6-rc5, Zdenek Kabelac
      • Re: [git pull] device mapper fixes for 5.6-rc5, Theodore Y. Ts'o
  • Re: [git pull] device mapper fixes for 5.6-rc5, pr-tracker-bot
• [PATCH] dm: fix congested_fn for request-based device, Hou Tao
  • Re: dm: fix congested_fn for request-based device, Mike Snitzer
    • Re: dm: fix congested_fn for request-based device, Hou Tao
• [PATCH 0/4] multipath-tools unit test fixups, mwilck
  • [PATCH 4/4] tests: add README.md, mwilck
  • [PATCH 3/4] tests/Makefile: add test_clean target, mwilck
  • [PATCH 2/4] tests/Makefile: allow setting DIO_TEST_DEV in the environment, mwilck
  • [PATCH 1/4] Remove tests/directio_test_dev, mwilck
  • Re: [PATCH 0/4] multipath-tools unit test fixups, Christophe Varoqui
    • Re: [PATCH 0/4] multipath-tools unit test fixups, Martin Wilck
      • Re: [PATCH 0/4] multipath-tools unit test fixups, Christophe Varoqui
  • Re: [PATCH 0/4] multipath-tools unit test fixups, Benjamin Marzinski
• multipath-tools merges, Christophe Varoqui
  • Re: multipath-tools merges, Martin Wilck
    • Re: multipath-tools merges, Christophe Varoqui
      • Re: multipath-tools merges, Martin Wilck
        • Re: multipath-tools merges, Christophe Varoqui
  • Re: multipath-tools merges, Benjamin Marzinski
• Re: [PATCH] crypto: caam - update xts sector size for large input length, Horia Geanta
• [dm:for-next 30/32] drivers/md/dm-bio-record.h:45:7: error: 'struct bio' has no member named 'bi_integrity'; did you mean 'bi_iter'?, kbuild test robot
• [PATCH v6 0/6] dax/pmem: Provide a dax operation to zero page range, Vivek Goyal
  • [PATCH v6 3/6] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
  • [PATCH v6 4/6] dm, dax: Add dax zero_page_range operation, Vivek Goyal
    • Re: [PATCH v6 4/6] dm, dax: Add dax zero_page_range operation, Dan Williams
      • Re: [PATCH v6 4/6] dm, dax: Add dax zero_page_range operation, Dan Williams
      • Re: [PATCH v6 4/6] dm, dax: Add dax zero_page_range operation, Mike Snitzer
  • [PATCH v6 2/6] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
    • Re: [PATCH v6 2/6] dax, pmem: Add a dax operation zero_page_range, Pankaj Gupta
  • [PATCH v6 1/6] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
    • Re: [PATCH v6 1/6] pmem: Add functions for reading/writing page to/from pmem, Pankaj Gupta
      • Re: [PATCH v6 1/6] pmem: Add functions for reading/writing page to/from pmem, Christoph Hellwig
      • Re: [PATCH v6 1/6] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
  • [PATCH v6 5/6] dax: Use new dax zero page method for zeroing a page, Vivek Goyal
  • [PATCH v6 6/6] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
  • Re: [PATCH v6 0/6] dax/pmem: Provide a dax operation to zero page range, Pankaj Gupta
  • Re: [PATCH v6 0/6] dax/pmem: Provide a dax operation to zero page range, Vivek Goyal
  • [PATCH v6 7/6] dax: Move mandatory ->zero_page_range() check in alloc_dax(), Vivek Goyal
• [PATCH] md/dm-stats.c: use list_for_each_entry*() APIs to simplify code, qiwuchen55
• [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Lukas Straub
  • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Mike Snitzer
    • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Lukas Straub
      • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Mike Snitzer
        • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Lukas Straub
  • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Mikulas Patocka
    • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Lukas Straub
    • Re: [PATCH v2] dm-integrity: Prevent RMW for full metadata buffer writes, Lukas Straub
• [PATCH] dm zoned: Fix reference counter initial value of chunk works, Shin'ichiro Kawasaki
  • Re: [PATCH] dm zoned: Fix reference counter initial value of chunk works, Damien Le Moal
• [PATCH] dm integrity: reinitialize __bi_remaining when reusing bio, Daniel Glöckner
  • Re: [PATCH] dm integrity: reinitialize __bi_remaining when reusing bio, Christoph Hellwig
    • Re: [PATCH] dm integrity: reinitialize __bi_remaining when reusing bio, Daniel Glöckner
      • Re: [PATCH] dm integrity: reinitialize __bi_remaining when reusing bio, Christoph Hellwig
        • Re: dm integrity: reinitialize __bi_remaining when reusing bio, Mike Snitzer
• [Job Posting] There is a position open in Red Hat for working on device-mapper, Brassow Jonathan
• [PATCH 1/7] dm: report suspended device during destroy, Mikulas Patocka
• [PATCH 7/7] dm writecache: optimize superblock write, Mikulas Patocka
• [PATCH 5/7] dm writecache: implement the "cleaner" policy, Mikulas Patocka
• [PATCH 4/7] dm writecache: do direct write if the cache is full, Mikulas Patocka
• [PATCH 2/7] dm-writecache: fix a crash when unloading, Mikulas Patocka
• [PATCH 6/7] dm-writecache: implement gradual cleanup, Mikulas Patocka
• [PATCH 0/7] dm-writecache patches, Mikulas Patocka
• [PATCH 3/7] dm writecache: verify watermark on resume, Mikulas Patocka
• [PATCH] dm-integrity: Prevent RMW for full tag area writes, Lukas Straub
  • Re: [PATCH] dm-integrity: Prevent RMW for full tag area writes, Mikulas Patocka
    • Re: [PATCH] dm-integrity: Prevent RMW for full tag area writes, Lukas Straub
      • Re: [PATCH] dm-integrity: Prevent RMW for full tag area writes, Mikulas Patocka
        • Re: [PATCH] dm-integrity: Prevent RMW for full tag area writes, Lukas Straub
• [PATCH] Remove WQ_CPU_INTENSIVE flag from unbound wq's, Maksym Planeta
  • Re: Remove WQ_CPU_INTENSIVE flag from unbound wq's, Mike Snitzer
    • Re: Remove WQ_CPU_INTENSIVE flag from unbound wq's, Maksym Planeta
      • Re: Remove WQ_CPU_INTENSIVE flag from unbound wq's, Song Liu
  • Re: [PATCH] Remove WQ_CPU_INTENSIVE flag from unbound wq's, Zhou Wang
  • Re: [PATCH] Remove WQ_CPU_INTENSIVE flag from unbound wq's, Gao Xiang
• [PATCH AUTOSEL 5.5 360/542] dm thin: don't allow changing data device during thin-pool reload, Sasha Levin
• [PATCH AUTOSEL 5.4 314/459] dm thin: don't allow changing data device during thin-pool reload, Sasha Levin
• [PATCH AUTOSEL 5.5 053/542] dm raid: table line rebuild status fixes, Sasha Levin
• [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
  • [PATCH v7 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
    • Re: [PATCH v7 6/6] loop: Add support for REQ_ALLOCATE, Darrick J. Wong
      • Re: [PATCH v7 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
  • [PATCH v7 3/6] block: Introduce blk_queue_get_max_write_zeroes_sectors(), Kirill Tkhai
  • [PATCH v7 5/6] block: Add blk_queue_max_allocate_sectors(), Kirill Tkhai
  • [PATCH v7 2/6] block: Pass op_flags into blk_queue_get_max_sectors(), Kirill Tkhai
  • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
    • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
      • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
        • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Christoph Hellwig
          • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Martin K. Petersen
            • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Darrick J. Wong
              • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Christoph Hellwig
                • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Martin K. Petersen
                  • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Christoph Hellwig
                    • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Martin K. Petersen
                      • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Christoph Hellwig
                        • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Chaitanya Kulkarni
          • Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
  • [PATCH v7 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
  • [PATCH v7 1/6] block: Add @flags argument to bdev_write_zeroes_sectors(), Kirill Tkhai
• [PATCH] dm crypt: use crypt_integrity_aead() helper, Yang Yingliang
• [PATCH v3] dm ebs: new block size emulating target, heinzm
  • Re: [PATCH v3] dm ebs: new block size emulating target, Damien Le Moal
    • Re: [PATCH v3] dm ebs: new block size emulating target, Heinz Mauelshagen
      • Re: [PATCH v3] dm ebs: new block size emulating target, Bryan Gurney
        • Re: [PATCH v3] dm ebs: new block size emulating target, Heinz Mauelshagen
          • Re: [PATCH v3] dm ebs: new block size emulating target, Damien Le Moal
      • Re: [PATCH v3] dm ebs: new block size emulating target, Damien Le Moal
• [PATCH v2 0/5] Multipath Follow-up patches, Benjamin Marzinski
  • [PATCH v2 5/5] libmultipath: cleanup old issues with directio checker, Benjamin Marzinski
  • [PATCH v2 1/5] multipath: fix issues found by compiling with gcc 10, Benjamin Marzinski
    • Re: [PATCH v2 1/5] multipath: fix issues found by compiling with gcc 10, Martin Wilck
    • Re: [PATCH v2 1/5] multipath: fix issues found by compiling with gcc 10, Martin Wilck
      • Re: [PATCH v2 1/5] multipath: fix issues found by compiling with gcc 10, Benjamin Marzinski
  • [PATCH v2 2/5] libmultipath: turn pp->vpd_data into a pointer, Benjamin Marzinski
  • [PATCH v2 3/5] libmultipath: change loading and resetting in directio, Benjamin Marzinski
  • [PATCH v2 4/5] libmultipath: change directio get_events() timeout handling, Benjamin Marzinski
• RFC: multipath-tools: NVMe native multipath and default setting for "enable_foreign", Martin Wilck
  • Re: RFC: multipath-tools: NVMe native multipath and default setting for "enable_foreign", Benjamin Marzinski
• [PATCH] dm cache: fix a crash due to incorrect work item canceling, Mikulas Patocka
• [PATCH 0/5] Multipath Follow-up patches, Benjamin Marzinski
  • [PATCH 2/5] libmultipath: turn pp->vpd_data into a pointer, Benjamin Marzinski
    • Re: [PATCH 2/5] libmultipath: turn pp->vpd_data into a pointer, Martin Wilck
  • [PATCH 3/5] libmultipath: change loading and resetting in directio, Benjamin Marzinski
    • Re: [PATCH 3/5] libmultipath: change loading and resetting in directio, Martin Wilck
      • Re: [PATCH 3/5] libmultipath: change loading and resetting in directio, Benjamin Marzinski
  • [PATCH 4/5] libmultipath: change directio get_events() timeout handling, Benjamin Marzinski
    • Re: [PATCH 4/5] libmultipath: change directio get_events() timeout handling, Martin Wilck
  • [PATCH 5/5] libmultipath: cleanup old issues with directio checker, Benjamin Marzinski
    • Re: [PATCH 5/5] libmultipath: cleanup old issues with directio checker, Martin Wilck
  • [PATCH 1/5] multipath: fix issues found by compiling with gcc 10, Benjamin Marzinski
    • Re: [PATCH 1/5] multipath: fix issues found by compiling with gcc 10, Martin Wilck
      • Re: [PATCH 1/5] multipath: fix issues found by compiling with gcc 10, Benjamin Marzinski
• [PATCH v3 00/18] Multipath patch dump, Benjamin Marzinski
  • [PATCH v3 01/18] multipathd: warn when configuration has been changed., Benjamin Marzinski
  • [PATCH v3 06/18] libmultipath: add missing hwe mpe variable merges, Benjamin Marzinski
  • [PATCH v3 02/18] multipathd: staticify uxlsnr variables/functions, Benjamin Marzinski
  • [PATCH v3 08/18] libmultipath: add vend_id to get_vpd_sgio, Benjamin Marzinski
  • [PATCH v3 04/18] libmultipath: remove unused path->prio_args, Benjamin Marzinski
  • [PATCH v3 05/18] libmultipath: constify get_unaligned_be*, Benjamin Marzinski
  • [PATCH v3 10/18] libmultipath: change how the checker async is set, Benjamin Marzinski
  • [PATCH v3 14/18] libmultipath: make directio checker share io contexts, Benjamin Marzinski
  • [PATCH v3 07/18] libmultipath: fix sgio_get_vpd looping, Benjamin Marzinski
  • [PATCH v3 09/18] libmultipath: add code to get vendor specific vpd data, Benjamin Marzinski
  • [PATCH v3 18/18] tests: make directio tests able to work on a real device, Benjamin Marzinski
  • [PATCH v3 11/18] libmultipath: change failed path prio timeout, Benjamin Marzinski
  • [PATCH v3 17/18] fixup! libmultipath: make directio checker share io contexts, Benjamin Marzinski
  • [PATCH v3 12/18] multipathd: add new paths under vecs lock, Benjamin Marzinski
  • [PATCH v3 15/18] tests: add directio unit tests, Benjamin Marzinski
  • [PATCH v3 13/18] libmultipath: add new checker class functions, Benjamin Marzinski
  • [PATCH v3 03/18] Fix leak in mpathpersist, Benjamin Marzinski
  • [PATCH v3 16/18] fixup! libmultipath: add code to get vendor specific vpd data, Benjamin Marzinski
  • Re: [PATCH v3 00/18] Multipath patch dump, Martin Wilck
• [PATCH v5 0/8] dax/pmem: Provide a dax operation to zero range of memory, Vivek Goyal
  • [PATCH v5 4/8] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
    • Re: [PATCH v5 4/8] dax, pmem: Add a dax operation zero_page_range, Dan Williams
      • Re: [PATCH v5 4/8] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
      • Re: [PATCH v5 4/8] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
  • [PATCH v5 3/8] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Vivek Goyal
    • Re: [PATCH v5 3/8] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Christoph Hellwig
  • [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Christoph Hellwig
    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
      • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
        • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
          • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
            • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                  • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
            • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dave Chinner
              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
                  • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
                      • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                        • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jeff Moyer
                          • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                        • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Jane Chu
              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dave Chinner
                  • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dave Chinner
                      • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                        • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Christoph Hellwig
                          • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                  • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                      • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                        • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                          • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                            • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dan Williams
                              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                              • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                                • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dave Chinner
                                  • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Vivek Goyal
                                    • Re: [PATCH v5 2/8] drivers/pmem: Allow pmem_clear_poison() to accept arbitrary offset and len, Dave Chinner
  • [PATCH v5 5/8] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
  • [PATCH v5 1/8] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
  • [PATCH v5 7/8] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
  • [PATCH v5 8/8] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
  • [PATCH v5 6/8] dm, dax: Add dax zero_page_range operation, Vivek Goyal
• [PATCH v4 0/7] dax/pmem: Provide a dax operation to zero range of memory, Vivek Goyal
  • [PATCH v4 3/7] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
    • Re: [PATCH v4 3/7] dax, pmem: Add a dax operation zero_page_range, Christoph Hellwig
  • [PATCH v4 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Vivek Goyal
    • Re: [PATCH v4 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Christoph Hellwig
      • Re: [PATCH v4 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Vivek Goyal
  • [PATCH v4 1/7] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
    • Re: [PATCH v4 1/7] pmem: Add functions for reading/writing page to/from pmem, Christoph Hellwig
  • [PATCH v4 4/7] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
  • [PATCH v4 7/7] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
  • [PATCH v4 5/7] dm, dax: Add dax zero_page_range operation, Vivek Goyal
  • [PATCH v4 6/7] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
• [PATCH] dm-integrity: fix invalid table returned, Mikulas Patocka
• [PATCH v2] dm integrity: fix a deadlock due to offloading to an incorrect workqueue (fwd), Mikulas Patocka
• question about multipathd patch thought., Roger Heflin
• 5.6-rc1 lockdep warning during dm-thin shutdown, Theodore Y. Ts'o
  • Re: 5.6-rc1 lockdep warning during dm-thin shutdown, Theodore Y. Ts'o
    • [PATCH] dm thin metadata: fix lockdep complaint, Theodore Ts'o
• [PATCH v2] dm ebs: new block size emulating target, heinzm
• [RFC PATCH 0/6] dax: Replace bdev_dax_pgoff() with dax_pgoff(), Vivek Goyal
  • [PATCH 3/6] fs/dax.c: Start using dax_pgoff() instead of bdev_dax_pgoff(), Vivek Goyal
  • [PATCH 2/6] dax, iomap, ext4, ext2, xfs: Save dax_offset in "struct iomap", Vivek Goyal
    • Re: [PATCH 2/6] dax, iomap, ext4, ext2, xfs: Save dax_offset in "struct iomap", Christoph Hellwig
  • [PATCH 5/6] drivers/dax: Use dax_pgoff() instead of bdev_dax_pgoff(), Vivek Goyal
  • [PATCH 4/6] dax, dm/md: Use dax_pgoff() instead of bdev_dax_pgoff(), Vivek Goyal
  • [PATCH 1/6] dax: Define a helper dax_pgoff() which takes in dax_offset as argument, Vivek Goyal
    • Re: [PATCH 1/6] dax: Define a helper dax_pgoff() which takes in dax_offset as argument, Christoph Hellwig
    • Re: [PATCH 1/6] dax: Define a helper dax_pgoff() which takes in dax_offset as argument, Matthew Wilcox
  • [PATCH 6/6] dax: Remove bdev_dax_pgoff() helper, Vivek Goyal
• [PATCH] dm-writecache: fix a crash when unloading, Mikulas Patocka
  • Re: [PATCH] dm-writecache: fix a crash when unloading, John Dorminy
    • Re: [PATCH] dm-writecache: fix a crash when unloading, Mikulas Patocka
• [PATCH] dm-integrity: print device name in integrity error message., device-mapper
• [PATCH] dm ebs: new block size emulating target, Heinz Mauelshagen
• [PATCH v6 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
  • [PATCH v6 1/6] block: Add @flags argument to bdev_write_zeroes_sectors(), Kirill Tkhai
  • [PATCH v6 2/6] block: Pass op_flags into blk_queue_get_max_sectors(), Kirill Tkhai
  • [PATCH v6 3/6] block: Introduce blk_queue_get_max_write_zeroes_sectors(), Kirill Tkhai
  • [PATCH v6 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
    • Re: [PATCH v6 4/6] block: Add support for REQ_ALLOCATE flag, Darrick J. Wong
      • Re: [PATCH v6 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
        • Re: [PATCH v6 4/6] block: Add support for REQ_ALLOCATE flag, Darrick J. Wong
          • Re: [PATCH v6 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
  • [PATCH v6 5/6] block: Add blk_queue_max_allocate_sectors(), Kirill Tkhai
  • [PATCH v6 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
    • Re: [PATCH v6 6/6] loop: Add support for REQ_ALLOCATE, Darrick J. Wong
      • Re: [PATCH v6 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
      • Re: [PATCH v6 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
        • Re: [PATCH v6 6/6] loop: Add support for REQ_ALLOCATE, Darrick J. Wong
• [PATCH 1/1] libmultipath: fix files read from config_dir, Enzo Matsumiya
  • Re: [PATCH 1/1] libmultipath: fix files read from config_dir, Martin Wilck
• [PATCH 1/2] dm-bufio: introduce block_to_sector, Mikulas Patocka
  • [PATCH 2/2] dm-bufio: introduce block_to_sector, Mikulas Patocka
• [PATCH v3 0/7] dax, pmem: Provide a dax operation to zero range of memory, Vivek Goyal
  • [PATCH v3 4/7] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
    • Re: [PATCH v3 4/7] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Gerald Schaefer
      • Re: [PATCH v3 4/7] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
        • Re: [PATCH v3 4/7] s390, dcssblk, dax: Add dax zero_page_range operation to dcssblk driver, Gerald Schaefer
  • [PATCH v3 3/7] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
    • Re: [PATCH v3 3/7] dax, pmem: Add a dax operation zero_page_range, Christoph Hellwig
      • Re: [PATCH v3 3/7] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
  • [PATCH v3 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Vivek Goyal
    • Re: [PATCH v3 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Christoph Hellwig
      • Re: [PATCH v3 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges, Vivek Goyal
  • [PATCH v3 1/7] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
    • Re: [PATCH v3 1/7] pmem: Add functions for reading/writing page to/from pmem, Christoph Hellwig
      • Re: [PATCH v3 1/7] pmem: Add functions for reading/writing page to/from pmem, Vivek Goyal
  • [PATCH v3 7/7] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
    • Re: [PATCH v3 7/7] dax, iomap: Add helper dax_iomap_zero() to zero a range, Christoph Hellwig
  • [PATCH v3 6/7] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
    • Re: [PATCH v3 6/7] dax, iomap: Start using dax native zero_page_range(), Christoph Hellwig
  • [PATCH v3 5/7] dm, dax: Add dax zero_page_range operation, Vivek Goyal
  • Re: [PATCH v3 0/7] dax, pmem: Provide a dax operation to zero range of memory, Vivek Goyal
• [PATCH] dm-bufio: implement discard, Mikulas Patocka
  • Re: [PATCH] dm-bufio: implement discard, John Dorminy
    • Re: [PATCH] dm-bufio: implement discard, Mikulas Patocka
      • Re: [PATCH] dm-bufio: implement discard, John Dorminy
        • Re: [PATCH] dm-bufio: implement discard, Mikulas Patocka
          • Re: [PATCH] dm-bufio: implement discard, John Dorminy
• [PATCH] dm-integrity: remove sector type casts, Mikulas Patocka
• [PATCH] dm-integrity: fix recalculation when moving from journal mode to bitmap mode, Mikulas Patocka
• [PATCH v2 00/17] Multipath patch dump, Benjamin Marzinski
  • [PATCH v2 01/17] multipathd: warn when configuration has been changed., Benjamin Marzinski
    • Re: [PATCH v2 01/17] multipathd: warn when configuration has been changed., Martin Wilck
  • [PATCH v2 04/17] Fix leak in mpathpersist, Benjamin Marzinski
  • [PATCH v2 06/17] libmultipath: constify get_unaligned_be*, Benjamin Marzinski
  • [PATCH v2 02/17] multipathd: staticify uxlsnr variables/functions, Benjamin Marzinski
    • Re: [PATCH v2 02/17] multipathd: staticify uxlsnr variables/functions, Martin Wilck
  • [PATCH v2 03/17] libmultipath: fix leak in foreign code, Benjamin Marzinski
    • Re: [PATCH v2 03/17] libmultipath: fix leak in foreign code, Martin Wilck
      • Re: [PATCH v2 03/17] libmultipath: fix leak in foreign code, Benjamin Marzinski
  • [PATCH v2 05/17] libmultipath: remove unused path->prio_args, Benjamin Marzinski
  • [PATCH v2 07/17] libmultipath: add missing hwe mpe variable merges, Benjamin Marzinski
  • [PATCH v2 08/17] libmultipath: fix sgio_get_vpd looping, Benjamin Marzinski
    • Re: [PATCH v2 08/17] libmultipath: fix sgio_get_vpd looping, Martin Wilck
  • [PATCH v2 13/17] multipathd: add new paths under vecs lock, Benjamin Marzinski
  • [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Benjamin Marzinski
    • Re: [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Martin Wilck
      • Re: [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Benjamin Marzinski
        • Re: [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Martin Wilck
          • Re: [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Benjamin Marzinski
    • Re: [PATCH v2 15/17] libmultipath: make directio checker share io contexts, Martin Wilck
  • [PATCH v2 11/17] libmultipath: change how the checker async is set, Benjamin Marzinski
  • [PATCH v2 12/17] libmultipath: change failed path prio timeout, Benjamin Marzinski
    • Re: [PATCH v2 12/17] libmultipath: change failed path prio timeout, Martin Wilck
  • [PATCH v2 10/17] libmultipath: add code to get vendor specific vpd data, Benjamin Marzinski
    • Re: [PATCH v2 10/17] libmultipath: add code to get vendor specific vpd data, Martin Wilck
      • Re: [PATCH v2 10/17] libmultipath: add code to get vendor specific vpd data, Benjamin Marzinski
        • Re: [PATCH v2 10/17] libmultipath: add code to get vendor specific vpd data, Martin Wilck
    • Re: [PATCH v2 10/17] libmultipath: add code to get vendor specific vpd data, Martin Wilck
  • [PATCH v2 16/17] tests: add directio unit tests, Benjamin Marzinski
    • Re: [PATCH v2 16/17] tests: add directio unit tests, Martin Wilck
  • [PATCH v2 14/17] libmultipath: add new checker class functions, Benjamin Marzinski
  • [PATCH v2 17/17] tests: make directio tests able to work on a real device, Benjamin Marzinski
    • Re: [PATCH v2 17/17] tests: make directio tests able to work on a real device, Martin Wilck
  • [PATCH v2 09/17] libmultipath: add vend_id to get_vpd_sgio, Benjamin Marzinski
  • Re: [PATCH v2 00/17] Multipath patch dump, Martin Wilck
    • Re: [PATCH v2 00/17] Multipath patch dump, Martin Wilck
• [PATCH] dm-writecache: fix allocation of devices on writecache tests, Mikulas Patocka
  • <Possible follow-ups>
  • Re: [PATCH] dm-writecache: fix allocation of devices on writecache tests, Mike Snitzer
• [RFC PATCH 0/5][V2] dax, pmem: Provide a dax operation to zero range of memory, Vivek Goyal
  • [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
    • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Christoph Hellwig
      • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
        • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Dan Williams
          • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Christoph Hellwig
            • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Dan Williams
              • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
                • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Dan Williams
          • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Vivek Goyal
            • Re: [PATCH 1/5] dax, pmem: Add a dax operation zero_page_range, Dan Williams
  • [PATCH 4/5] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
    • Re: [PATCH 4/5] dax, iomap: Start using dax native zero_page_range(), Christoph Hellwig
      • Re: [PATCH 4/5] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
      • Re: [PATCH 4/5] dax, iomap: Start using dax native zero_page_range(), Vivek Goyal
  • [PATCH 5/5] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
    • Re: [PATCH 5/5] dax, iomap: Add helper dax_iomap_zero() to zero a range, kbuild test robot
    • Re: [PATCH 5/5] dax, iomap: Add helper dax_iomap_zero() to zero a range, Christoph Hellwig
      • Re: [PATCH 5/5] dax, iomap: Add helper dax_iomap_zero() to zero a range, Vivek Goyal
  • [PATCH 3/5] dm,dax: Add dax zero_page_range operation, Vivek Goyal
    • Re: [PATCH 3/5] dm, dax: Add dax zero_page_range operation, Christoph Hellwig
      • Re: [PATCH 3/5] dm, dax: Add dax zero_page_range operation, Vivek Goyal
  • [PATCH 2/5] s390, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
    • Re: [PATCH 2/5] s390, dax: Add dax zero_page_range operation to dcssblk driver, Christoph Hellwig
      • Re: [PATCH 2/5] s390, dax: Add dax zero_page_range operation to dcssblk driver, Vivek Goyal
• [PATCH] dm: expose dm_copy_name_and_uuid(), John Dorminy
  • Re: dm: expose dm_copy_name_and_uuid(), Mike Snitzer
    • Re: dm: expose dm_copy_name_and_uuid(), John Dorminy
      • Re: dm: expose dm_copy_name_and_uuid(), Alasdair G Kergon
        • Re: dm: expose dm_copy_name_and_uuid(), Alasdair G Kergon
          • Re: dm: expose dm_copy_name_and_uuid(), John Dorminy
            • Re: dm: expose dm_copy_name_and_uuid(), Mike Snitzer
• [PATCH 2/3] dm-integrity: introduce get_provided_data_sectors, Mikulas Patocka
• [PATCH 3/3] dm-integrity: change the size of the device, Mikulas Patocka
• [PATCH 0/3] dm-integrity: make it possible to change the size of dm-integrity device, Mikulas Patocka
• [PATCH 1/3] dm-integrity: dont replay journal data past the end of the device, Mikulas Patocka
• [git pull] device mapper changes for 5.6, Mike Snitzer
  • Re: [git pull] device mapper changes for 5.6, pr-tracker-bot
• [PATCH 0/1] Handle NULL make_request_fn in generic_make_request(), Stefan Bader
  • [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Stefan Bader
    • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Mike Snitzer
      • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Mike Snitzer
        • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Jens Axboe
          • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Stefan Bader
          • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Mike Snitzer
            • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Jens Axboe
            • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Stefan Bader
              • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Mike Snitzer
    • Re: [PATCH 1/1] blk/core: Gracefully handle unset make_request_fn, Tyler Hicks
• [PATCH v5 0/6] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
  • [PATCH v5 6/6] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
  • [PATCH v5 1/6] block: Add @flags argument to bdev_write_zeroes_sectors(), Kirill Tkhai
  • [PATCH v5 5/6] block: Add blk_queue_max_allocate_sectors(), Kirill Tkhai
  • [PATCH v5 2/6] block: Pass op_flags into blk_queue_get_max_sectors(), Kirill Tkhai
    • Re: [PATCH v5 2/6] block: Pass op_flags into blk_queue_get_max_sectors(), Bob Liu
      • Re: [PATCH v5 2/6] block: Pass op_flags into blk_queue_get_max_sectors(), Kirill Tkhai
  • [PATCH v5 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
    • Re: [PATCH v5 4/6] block: Add support for REQ_ALLOCATE flag, Bob Liu
      • Re: [PATCH v5 4/6] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
  • [PATCH v5 3/6] block: Introduce blk_queue_get_max_write_zeroes_sectors(), Kirill Tkhai
    • Re: [PATCH v5 3/6] block: Introduce blk_queue_get_max_write_zeroes_sectors(), Bob Liu
• [PATCH v4 0/7] block: Introduce REQ_ALLOCATE flag for REQ_OP_WRITE_ZEROES, Kirill Tkhai
  • [PATCH v4 4/7] block: Add support for REQ_ALLOCATE flag, Kirill Tkhai
  • [PATCH v4 7/7] loop: Add support for REQ_ALLOCATE, Kirill Tkhai
  • [PATCH v4 1/7] block: Add @flags argument to bdev_write_zeroes_sectors(), Kirill Tkhai
  • [PATCH v4 5/7] block: Add blk_queue_max_allocate_sectors(), Kirill Tkhai
  • [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now, Kirill Tkhai
    • Re: [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now, Mike Snitzer
      • Re: [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now, Kirill Tkhai
        • Re: [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now, Kirill Tkhai
          • Re: [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now, Mike Snitzer