Linux Device-Mapper Development

• Thread Index

• Re: [PATCH] dm-mpath: Work with blk multi-queue drivers
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 2/2] dm-raid: add 'no_discard_passdown' table argument
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/2] dm-raid: add RAID discard support
  • From: heinzm@xxxxxxxxxx
• Re: [PATCH] dm-raid: add RAID discard support
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH] dm-mpath: Work with blk multi-queue drivers
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: reply： Thinly-Provisioned Logical Volumes
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] dm-mpath: Work with blk multi-queue drivers
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: 3PAR transparent failover with Linux
  • From: Thomas Glanzmann <thomas@xxxxxxxxxxxx>
• Re: reply： Thinly-Provisioned Logical Volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [data] Re: [linux-lvm] Setting up LVM cache causes crash
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RHEL6.6 dm-cache and dm-era
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: 3PAR transparent failover with Linux
  • From: Thomas Glanzmann <thomas@xxxxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• reply： Thinly-Provisioned Logical Volumes
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: DM-Multipath limiting IO to 127.000 MB/Sec
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: 3PAR transparent failover with Linux
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm-raid: add RAID discard support
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: DM-Multipath limiting IO to 127.000 MB/Sec
  • From: Ali Poursamadi <ali@xxxxxxxxxxxxxx>
• [PATCH] dm-raid: add RAID discard support
  • From: heinzm@xxxxxxxxxx
• Re: DM-Multipath limiting IO to 127.000 MB/Sec
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: reply： Thinly-Provisioned Logical Volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• reply： Thinly-Provisioned Logical Volumes
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: [PATCH v4 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Dmitry Kasatkin <d.kasatkin@xxxxxxxxxxx>
• [PATCH v4 08/12] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 10/12] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 00/12] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 06/12] crypto: LLVMLinux: Remove VLAIS from crypto/omap_sham.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 03/12] crypto: LLVMLinux: Remove VLAIS from crypto/ccp/ccp-crypto-sha.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 09/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 12/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 05/12] crypto: LLVMLinux: Remove VLAIS from crypto/n2_core.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 07/12] crypto: LLVMLinux: Remove VLAIS from crypto/.../qat_algs.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 04/12] crypto: LLVMLinux: Remove VLAIS from crypto/mv_cesa.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• DM-Multipath limiting IO to 127.000 MB/Sec
  • From: Ali Poursamadi <ali@xxxxxxxxxxxxxx>
• Re: Shared Memory Pages for Same Base Device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Shared Memory Pages for Same Base Device
  • From: Shao Miller <shao.miller@xxxxxxxxxxx>
• Re: Shared Memory Pages for Same Base Device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Thinly-Provisioned Logical Volumes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RHEL6.6 dm-cache and dm-era
  • From: Romu <huruomu@xxxxxxxxx>
• Re: Thinly-Provisioned Logical Volumes
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: NeilBrown <neilb@xxxxxxx>
• Shared Memory Pages for Same Base Device
  • From: Shao Miller <shao.miller@xxxxxxxxxxx>
• Thinly-Provisioned Logical Volumes
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm: alternate solution to reloading with failed paths
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/2] dm: allow active and inactive tables to share dm_devs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 0/2] dm: alternate solution to reloading with failed paths
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 1/2] dm mpath: stop queueing IO when no valid paths exist
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 2/2] dm: allow active and inactive tables to share dm_devs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RHEL6.6 dm-cache and dm-era
  • From: Romu Hu <huruomu@xxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: "Liuhua Wang" <lwang@xxxxxxxx>
• Re: [PATCH v3 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: Chris Mason <clm@xxxxxx>
• [PATCH] dm crypt: retain write ordering
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Dmitry Kasatkin <d.kasatkin@xxxxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: "Liuhua Wang" <lwang@xxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] fix mirror device creation with lvcreate failed
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 0/2] dm: alternate solution to reloading with failed paths
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: partx fails 4096 block size
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: partx fails 4096 block size
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/2] dm: alternate solution to reloading with failed paths
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RHEL6.6 dm-cache and dm-era
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• partx fails 4096 block size
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Michał Mirosław <mirqus@xxxxxxxxx>
• [PATCH v3 09/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 07/12] crypto: LLVMLinux: Remove VLAIS from crypto/.../qat_algs.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 00/12] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 03/12] crypto: LLVMLinux: Remove VLAIS from crypto/ccp/ccp-crypto-sha.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 05/12] crypto: LLVMLinux: Remove VLAIS from crypto/n2_core.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 04/12] crypto: LLVMLinux: Remove VLAIS from crypto/mv_cesa.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 08/12] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 10/12] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 06/12] crypto: LLVMLinux: Remove VLAIS from crypto/omap_sham.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 12/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• Re: Powerpath vs dm-multipath - two points of FUD?
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] slab: implement kmalloc guard
  • From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>
• Re: Powerpath vs dm-multipath - two points of FUD?
  • From: "Levy, Jerome" <jerome.levy@xxxxxxx>
• RHEL6.6 dm-cache and dm-era
  • From: Romu Hu <huruomu@xxxxxxxxx>
• Re: [PATCH 5/6] multipath.conf: add all_devs device option
  • From: Nir Soffer <nsoffer@xxxxxxxxxx>
• Re: [PATCH 0/6] Misc multipath patches
  • From: Nir Soffer <nsoffer@xxxxxxxxxx>
• Re: Powerpath vs dm-multipath - two points of FUD?
  • From: Hannes Reinecke <hare@xxxxxxx>
• [BUG] dm-writeboost: Don't pass __GFP_ZERO to mempool_alloc()
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 0/6] Misc multipath patches
  • From: Nir Soffer <nsoffer@xxxxxxxxxx>
• Re: [PATCH 0/6] Misc multipath patches
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [git pull] device mapper fix for 3.17-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/6] Fix missing frees and null terminations
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 5/6] multipath.conf: add all_devs device option
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 3/6] libmultipath: Add additional path wildcards
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 2/6] Add support for EMC XtremIO
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 1/6] libmultipath: cleanup rlookup_binding
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 0/6] Misc multipath patches
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 6/6] Always put watchdog in the config structure
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH] dm crypt: fix access beyond the end of allocated space
  • From: Willy Tarreau <w@xxxxxx>
• Re: [PATCH] slab: implement kmalloc guard
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm crypt: fix access beyond the end of allocated space
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• 3PAR transparent failover with Linux
  • From: Thomas Glanzmann <thomas@xxxxxxxxxxxx>
• Re: Powerpath vs dm-multipath - two points of FUD?
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 1/1] fix build, replace GZIP with GZIPCMD
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [PATCH 1/1] fix build, replace GZIP with GZIPCMD
  • From: Christian Hesse <mail@xxxxxxxx>
• Powerpath vs dm-multipath - two points of FUD?
  • From: Rob <robertfreeman83@xxxxxxxxx>
• Re: dm-thin - issue about the maximum size of the metadata device
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-thin - issue about the maximum size of the metadata device
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache caching network volume
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm cache: fix race causing dirty blocks to be marked as clean
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] slab: implement kmalloc guard
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: implement kmalloc guard
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: implement kmalloc guard
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] crypto: memzero_explicit - make sure to clear out sensitive data
  • From: Daniel Borkmann <dborkman@xxxxxxxxxx>
• Re: [PATCH] crypto: memzero_explicit - make sure to clear out sensitive data
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH] slab: implement kmalloc guard
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• lvmetad in initrd hangs, blocking further lvm calls
  • From: Bastien Durel <bastien+lvm@xxxxxxxxx>
• [PATCH] dm cache: fix race causing dirty blocks to be marked as clean
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: [ANNOUNCE] thin-provisioning-tools v0.4.0
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [ANNOUNCE] thin-provisioning-tools v0.4.0
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• [PATCH] libmultipath: Typo in condlog in select_flush_on_last_del
  • From: Bernhard Reutner-Fischer <rep.dot.nop@xxxxxxxxx>
• Re: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: Jan-Simon Möller <dl9pf@xxxxxx>
• Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• [PATCH RFC 6/6] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 2/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 3/6] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 1/6] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 4/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• Re: [PATCH] libmultipath: Typo in condlog in select_flush_on_last_del
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [git pull] device mapper fix for 3.17
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH RFCv2 10/10] dm-dedup: documentation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 05/10] dm-dedup: COW B-tree backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 04/10] dm-dedup: implementation of the read-on-write procedure
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 07/10] dm-dedup: Makefile changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 06/10] dm-dedup: inram backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 08/10] dm-dedup: Kconfig changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 03/10] dm-dedup: hash computation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFCv2 09/10] dm-dedup: status function
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix access beyond the end of allocated space
  • From: Krzysztof Kolasa <kkolasa@xxxxxxxxxx>
• Re: dm-crypt: Fix access beyond the end of allocated space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix access beyond the end of allocated space
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] dm-crypt: Fix access beyond the end of allocated space
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm-crypt: Fix per-bio data alignment
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] fix mirror device creation with lvcreate failed
  • From: Liuhua Wang <lwang@xxxxxxxx>
• [PATCH] libmultipath: Fix typo in log message of execute_program()
  • From: Ferenc Wágner <wferi@xxxxxxx>
• Re: [PATCH] libmultipath: Fix typo in log message of execute_program()
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 22/30] multipath: Implement 'property' blacklist
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 22/30] multipath: Implement 'property' blacklist
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: convert dm_ulog_request data to little endian
  • From: zhangdongmao <dmzhang@xxxxxxxx>
• Re: convert dm_ulog_request data to little endian
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] convert dm_ulog_request data to little endian
  • From: zhangdongmao <dmzhang@xxxxxxxx>
• Re: [PATCH] convert dm_ulog_request data to little endian
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] convert dm_ulog_request data to little endian
  • From: zhangdongmao <dmzhang@xxxxxxxx>
• Re: [PATCH] convert dm_ulog_request data to little endian
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix per-bio data alignment
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix per-bio data alignment
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix per-bio data alignment
  • From: Krzysztof Kolasa <kkolasa@xxxxxxxxxx>
• [PATCH] dm-crypt: Fix per-bio data alignment
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
  • From: Krzysztof Kolasa <kkolasa@xxxxxxxxxx>
• Re: commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• commit 298a9fa dm crypt: use per-bio data hard crash kernel ( the system freezes )
  • From: Krzysztof Kolasa <kkolasa@xxxxxxxxxx>
• Re: [PATCH] dm cache: fix race affecting dirty block count
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: dm: propagate QUEUE_FLAG_NO_SG_MERGE
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] dm-multipath: cleanup IO queueing after table load
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-multipath: cleanup IO queueing after table load
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/2] dm-multipath: cleanup IO queueing after table load
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 2/2] device-mapper: allow tables to share dm_devs
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 0/2] dm: alternate solution to reloading with failed paths
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [git pull] device mapper changes for 3.17
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath-tools: Potential issue in blacklist entry handling
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: dm: propagate QUEUE_FLAG_NO_SG_MERGE
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: convert dm_ulog_request data to little endian
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: convert dm_ulog_request data to little endian
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: propagate QUEUE_FLAG_NO_SG_MERGE
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch] dm: propagate QUEUE_FLAG_NO_SG_MERGE
  • From: Greg KH <greg@xxxxxxxxx>
• [patch] dm: propagate QUEUE_FLAG_NO_SG_MERGE
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• [PATCH] convert dm_ulog_request data to little endian
  • From: Dongmao Zhang <dmzhang@xxxxxxxx>
• multipath-tools: Potential issue in blacklist entry handling
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH] dm cache: fix race affecting dirty block count
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• [git pull] device mapper fixes for 3.16 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm cache: fix race affecting dirty block count
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [dm-crypt] LUKS on a jffs2 partition
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 0/2] dm-switch: quickly load repetitive pattern
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm cache: fix race affecting dirty block count
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: [PATCH 0/2] dm-switch: quickly load repetitive pattern
  • From: Mike Snitzer <msnitzer@xxxxxxxxxx>
• Re: [PATCH] dm bufio: fully initialize shrinker
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm bufio: fully initialize shrinker
  • From: Greg Thelen <gthelen@xxxxxxxxxx>
• [PATCH 2/2 v2] dm-switch: allow repetitive patterns
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm-switch: quickly load repetitive pattern
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm-switch: introdice switch_region_table_read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-switch: quickly load repetitive pattern
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/2] dm-switch: quickly load repetitive pattern
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/2] dm-switch: allow repetitive patterns
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Status of SCSI referrals support in dm-multipath
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 2/2] arm aes: fix encryption of unaligned data
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• dm-cache race on nr_dirty in set_dirty/clear_dirty?
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• [PATCH 2/2] arm aes: fix encryption of unaligned data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] arm64 aes: fix encryption of unaligned data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/5] libmultipath: Print line number for which parsing failed
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 5/5] libmultipath: Accept "*" as a valid regular expression
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 5/5] libmultipath: Accept "*" as a valid regular expression
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 5/5] libmultipath: Accept "*" as a valid regular expression
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 4/5] libmultipath: Print line number for which parsing failed
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 1/5] ALUA prioritizer: Remove an unused variable
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: multipath and READ_CAPACITY
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 12/12] Add multipath.conf force_sync option
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 11/12] make prioritizers use checker_timeout, if set
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 10/12] Improve multipath.conf syntax checking
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• multipath and READ_CAPACITY
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 09/12] orphan paths on failed add
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 07/12] Make multipathd orphan paths that were removed externally
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] multipath: add option '-i' to ignore wwids file
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH]multipath: Wrong sysfs attribute used for iSCSI settings.
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 0/5] Five small multipath-tools patches
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [RFC] dm-writeboost: Removing a tunable barrier_deadline_ms
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• [patch] slab_common: fix the check for duplicate slab names
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps)
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• [git pull] stable mm/slab_common.c fix for 3.16-rc7
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• are the dm target ioctl handlers extensible to serving arbitrary configuration ioctls?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: [PATCH] multipath: revert fstack-protector-strong gcc option
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm-writeboost: Remove unsure BUG() from init_rambuf_pool
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps)
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: multipath-tools: -fstack-protector to fstack-protector-strong change
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] multipath: revert fstack-protector-strong gcc option
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: multipath-tools: -fstack-protector to fstack-protector-strong change
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps)
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: Does multipath require disabled write cache?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• multipath-tools: -fstack-protector to fstack-protector-strong change
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps)
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] dm-writeboost: Remove unsure BUG() from init_rambuf_pool
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• dm-cache-policy-mq.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Does multipath require disabled write cache?
  • From: Spelic <spelic@xxxxxxxxxxxxx>
• Re: [PATCH] dm-writeboost: Remove unsure BUG() from init_rambuf_pool
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm-writeboost: Remove unsure BUG() from init_rambuf_pool
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• Re: [BUG] dm-writeboost: too big nr_rambuf_pool causes massive memory pressure or panic.
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• Re: dm thin: set {minimum, optimal}_io_size to pool's data block size
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: set {minimum, optimal}_io_size to pool's data block size
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Tomas Henzl <thenzl@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH 5/5] libmultipath: Accept "*" as a valid regular expression
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 4/5] libmultipath: Print line number for which parsing failed
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 3/5] libmultipath: Zero-terminate sysfs_attr_get_value() result
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 1/5] ALUA prioritizer: Remove an unused variable
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 2/5] libmultipath: Simplify read_line()
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 0/5] Five small multipath-tools patches
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [dm-crypt] LUKS on a jffs2 partition
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.16-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [BUG] dm-writeboost: too big nr_rambuf_pool causes massive memory pressure or panic.
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] writeboost: rename "migration" to "writeback"
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/15] block copy: use asynchronous notification
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/15] dm: introduce dm_ask_for_duplicate_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 14/15] dm kcopyd: change mutex to spinlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 10/15] dm linear: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 13/15] dm kcopyd: support copy offload
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 12/15] dm kcopyd: introduce the function submit_job
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 11/15] dm stripe: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 9/15] dm: implement copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/15] dm: remove num_write_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/15] block copy: use merge_bvec_fn for copies
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/15] block copy: report the amount of copied data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/15] block copy: use two bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: insitu-comp
  • From: testfile82 <testfile82@xxxxxxxxxxx>
• [BUG] dm-writeboost: too big nr_rambuf_pool causes massive memory pressure or panic.
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• [RFC] writeboost: rename "migration" to "writeback"
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.16-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• kpartx bug when using very long paths?
  • From: Patrick Schleizer <patrick-mailinglists@xxxxxxxxxx>
• [PATCH v2] dm-table: make dm_table_supports_discards static
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-table: make dm_table_supports_discards static
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Alexey Kardashevskiy <aik@xxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "xinhui.pan" <xinhuix.pan@xxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix an error code in local_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch] dm: fix an error code in local_init()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] multipath: add option '-i' to ignore wwids file
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "xinhui.pan" <xinhuix.pan@xxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] multipath: add option '-i' to ignore wwids file
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 03/12] enable gcc format-security check
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 05/12] allow users to add wwids to /etc/multipath/wwids with -a
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 04/12] change conf->dry_run to conf->cmd
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 03/12] enable gcc format-security check
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 02/12] Return the correct size buffer in set_value()
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] Don't forget to reload table when both reload and rename is required
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 01/12] Fix memory issues in path reordering failure code paths
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] check info.exists to get valid value
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] Update ETERNUS DX entry
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: huangminfei <huangminfei@xxxxxxxxx>
• Re: [PATCH] dm-io: Fix a race condition in the wake up code for sync_io
  • From: huangminfei <huangminfei@xxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: huangminfei <huangminfei@xxxxxxxxx>
• [PATCH] dm-io: Fix a race condition in the wake up code for sync_io
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Marc Lehmann <schmorp@xxxxxxxxxx>
• [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 05/12] allow users to add wwids to /etc/multipath/wwids with -a
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 08/12] Add missing interactive commands to multipathd man page
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 00/12] miscellaneous multipath patches
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 01/12] Fix memory issues in path reordering failure code paths
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 11/12] make prioritizers use checker_timeout, if set
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 03/12] enable gcc format-security check
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 04/12] change conf->dry_run to conf->cmd
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 12/12] Add multipath.conf force_sync option
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 07/12] Make multipathd orphan paths that were removed externally
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 02/12] Return the correct size buffer in set_value()
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 10/12] Improve multipath.conf syntax checking
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 09/12] orphan paths on failed add
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] check info.exists to get valid value
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• [PATCH] Don't forget to reload table when both reload and rename is required
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• Re: dmdedup target mkfs.ext3 failed
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• dmdedup target mkfs.ext3 failed
  • From: lvshuo <testfile82@xxxxxxxxxxx>
• LVM2 release 2.02.107: New argument --select
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH]multipath: Wrong sysfs attribute used for iSCSI settings.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm: allocate a special workqueue for deferred remove
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [git pull] device mapper changes for 3.16
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-thin: Export proper discard_granularity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-thin: Export proper discard_granularity
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-thin: Export proper discard_granularity
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH] kpartx: fix extended partition size for >512b sectors
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH]multipath-tools: Mismatch between allocation length and transfer length in rdac prio
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH] kpartx: fix extended partition size for >512b sectors
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 5/7] dm: move free_rq_clone() out of dm_unprep_request()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 7/7] dm: do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/7] dm: use dm_rq_target_io as argument for dm_done()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 3/7] dm: move rq_completed() out of enclosing functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 6/7] dm: open-code free_rq_clone()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 4/7] dm: open-code dm_kill_unmapped_request()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/7] dm: remove handling of DM_ENDIO_INCOMPLETE
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: good dm-mpath test setup?
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: good dm-mpath test setup?
  • From: Hannes Reinecke <hare@xxxxxxx>
• good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: 3.13-1 dm cache possible race condition
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Persistent Overlay COW Full: Flipped the Invalid bit in a hexdump; how do I grow it now?
  • From: Frederick Grose <fgrose@xxxxxxxxx>
• Persistent Overlay COW Full: Flipped the Invalid bit in a hexdump; how do I grow it now?
  • From: Rahul Nabar <rpnabar@xxxxxxxxx>
• dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Status of SCSI referrals support in dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Status of SCSI referrals support in dm-multipath
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm linear: disable WRITE SAME if it fails
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm linear: disable WRITE SAME if it fails
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm linear: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• [git pull] device mapper fixes for 3.15 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch] DM RAID: fix a couple integer overflows
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
• Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: block: flush queued bios when the process blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Problem with overlay free space
  • From: Ришат Терегулов <rtereguloff@xxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Pekka Enberg <penberg@xxxxxx>
• [PATCH] md: Use time_in_range()
  • From: Manuel Schölling <manuel.schoelling@xxxxxx>
• Re: [PATCH v2] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writeboost: Progress Report
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH v2] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: Re-using bio
  • From: Enoch Root <enokhroot@xxxxxxxxx>
• Re-using bio
  • From: Enoch Root <enokhroot@xxxxxxxxx>
• Re: [PATCH] multipath: Fix some minor issues in path reordering code
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] multipath: Fix some minor issues in path reordering code
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm: check era->md is non-NULL before closing it
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] dm: check era->md is non-NULL before closing it
  • From: naota@xxxxxxxxx
• [PATCH]multipath-tools: Mismatch between allocation length and transfer length in rdac prio
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: Status of Linux LVM thin provisioning
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Status of Linux LVM thin provisioning
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: thin_repair doesn't do size checking on the output device
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Status of Linux LVM thin provisioning
  • From: Patrik Horník <patrik@xxxxxx>
• thin_repair doesn't do size checking on the output device
  • From: "M.H. Tsai" <mingnus@xxxxxxxxx>
• dm-writeboost: Progress Report
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [git pull] device mapper fixes for 3.15-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: Problem with multipath
  • From: Tommaso <tomcec@xxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: path coalescing once more
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: path coalescing once more
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• path coalescing once more
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Performance question when blocks in thin-pool are assume zeroed
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Performance question when blocks in thin-pool are assume zeroed
  • From: Wayne Chou <gmmark12@xxxxxxxxx>
• Performance question when blocks in thin-pool are assume zeroed
  • From: Wayne Chou <gmmark12@xxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: allow metadata commit if pool is in PM_OUT_OF_DATA_SPACE mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: are there usage examples for dm_sm_metadata_{create|open}?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: are there usage examples for dm_sm_metadata_{create|open}?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: "John L. Utz III (WDC)" <john.utz@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: John Utz <John.Utz@xxxxxxx>
• are there usage examples for dm_sm_metadata_{create|open}?
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.15-rc4
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix segfault when fast_io_fail_tmo is empty in config file.
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] Fix segfault when fast_io_fail_tmo is empty in config file.
  • From: Jose Castillo <jcastillo@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH RFC 08/10] dm-dedup: Kconfig changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 02/10] dm-dedup: core deduplication logic
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 03/10] dm-dedup: hash computation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 04/10] dm-dedup: implementation of the read-on-write procedure
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 10/10] dm-dedup: documentation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 01/10] dm-dedup: main data structures
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 05/10] dm-dedup: COW B-tree backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 09/10] dm-dedup: status function
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 06/10] dm-dedup: inram backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 07/10] dm-dedup: Makefile changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Lukáš Czerner <lczerner@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• path coalescing problems revisited
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• a problem about dm_kcopyd_copy()
  • From: lihuiba <magazine.lihuiba@xxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: dm-verity: Fix biovecs hash calculation regression
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Fix biovecs hash calculation regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-verity: Fix biovecs hash calculation regression
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: path coalescing in multipath
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: path coalescing in multipath
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• path coalescing in multipath
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Correct Routing Setup for Multipath
  • From: Eric K <iggiggitoo@xxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• kpartx -d fails to delete partition mapping for long filenames
  • From: "Carsten Scholtes" <Carsten_Scholtes@xxxxxxx>
• not able to find dm-integrity source code
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• not able to find dm-integrity source code
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: block: use kmalloc alignment for bio slab
  • From: Jens Axboe <axboe@xxxxxx>
• dm-integrity source code link?
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: block: use kmalloc alignment for bio slab
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-verity usage help related
  • From: Shivaramakrishnan Vaidyanathan <shivaramakrishnan740@xxxxxxxxx>
• dm-verity usage understanding
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 9/9] dm-crypt: sort writes
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/9] dm-crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/9] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/9] dm-crypt: remove io_pool
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/9] dm-crypt: don't allocate pages for a partial request
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/9] dm-crypt: use unbound workqueue for request processing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/9] bio: use kmalloc alignment for bio slab
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/9] dm-crypt: use per-bio data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/9] dm-crypt: remove per-cpu structure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>