Linux Device-Mapper Development

• Thread Index

• Re: [PATCH v3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3] block, dm: don't copy bios for request clones
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/1] dm: do not allocate any mempools for blk-mq request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm stripe: drop useless exit point from dm_stripe_init()
  • From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] block, dm: don't copy bios for request clones
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Christoph Hellwig <hch@xxxxxx>
• Possible Bottleneck in dm-cache
  • From: Greg Walters <greg.walters@xxxxxxxxxxxxxxxx>
• Re: Device mapper failed to open temporary keystore device
  • From: Murilo Opsfelder Araújo <mopsfelder@xxxxxxxxx>
• Re: [PATCH] libmultipath: fix discovery of devices with sysfs attr containing only spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] [RESEND]dm-raid1: several fixes about writing on out of sync mirror device
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• Re: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• Re: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH 3/3] raid0: conditional mddev->queue access to suit dm-raid
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH 2/3] dm core: export dm_disk to allow for dm-raid to pass it on to the MD raid0 personality
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH 1/3] dm-raid: Add support for the MD RAID0 personality
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Device mapper failed to open temporary keystore device
  • From: Murilo Opsfelder Araújo <mopsfelder@xxxxxxxxx>
• Device mapper failed to open temporary keystore device
  • From: Murilo Opsfelder Araújo <mopsfelder@xxxxxxxxx>
• Re: Device mapper failed to open temporary keystore device
  • From: Murilo Opsfelder Araújo <mopsfelder@xxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• dm log: struct log_write_super and padding (was: Re: dm: add log writes target)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH] dm log: Use ULL suffix for 64-bit constants
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: Device mapper failed to open temporary keystore device
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Device mapper failed to open temporary keystore device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/3] dm core: export dm_disk to allow for dm-raid to pass it on to the MD raid0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/3] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH 3/3] raid0: conditional mddev->queue access to suit dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/3] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• [PATCH 5/7] md: use block_device name vsprintf helper v2
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 4/7] fs: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 6/7] block/partitions: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 7/7] drivers: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 2/7] lib/vsprintf: add %*pg format specifier
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 0/7] fs: add blkdev name format specifier v2
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 3/7] block: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 1/7] fs: use gendisk->disk_name where possible
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm crypt: fix error return code in crypt_ctr()
  • From: weiyj_lk@xxxxxxx
• [PATCH] libmultipath: Add prioritizer context data
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [git pull] device mapper changes for 4.1
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] [RESEND]dm-raid1: several fixes about writing on out of sync mirror device
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• [PATCH 3/3] dm-raid1: change default mirror when it's not in sync
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH 2/3] dm-raid1: remove the error flags in the mirror set when it's in sync
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH 0/3] [RESEND]dm-raid1: several fixes about writing on out of sync mirror device
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH 1/3] dm-raid1: fix the parameter passed into the kernel
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH] dm-raid1: change default mirror when it's not in sync
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH] dm-raid1: several fixes about writing on out of sync mirror device
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH] dm-raid1: remove the error flags in the mirror set when it's in sync
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH] dm-raid1: fix the parameter passed into the kernel
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH 5/7] md: use block_device name vsprintf helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 7/7] drivers: use block_device name vsprintf helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 6/7] block/partitions: use block_device name vsprintf helper v2
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 4/7] fs: use block_device name vsprintf helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 3/7] block: use block_device name vsprintf helper
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 2/7] lib/vsprintf: add %*pg format specifier
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/7] fs: use gendisk->disk_name where possible
  • From: Jan Kara <jack@xxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Thomas Wouters <thomas@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• ALUA - rescan device capacity on zero sized block devices
  • From: Thomas Wouters <thomas@xxxxxxxxxxxxx>
• [PATCH 4/7] fs: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 5/7] md: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 2/7] lib/vsprintf: add %*pg format specifier
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 0/7] fs: add blkdev name format specifier v2
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 3/7] block: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 1/7] fs: use gendisk->disk_name where possible
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 7/7] drivers: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 6/7] block/partitions: use block_device name vsprintf helper v2
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: [f2fs-dev] [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Ben Collins <ben.c@xxxxxxxxxxxx>
• Re: [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Ben Collins <ben.c@xxxxxxxxxxxx>
• the multipath for EMC CX700
  • From: "wuyi@xxxxxxxxxx" <wuyi@xxxxxxxxxx>
• Re: [PATCH] libmultipath: fix discovery of devices with sysfs attr containing only spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• [PATCH] libmultipath: fix discovery of devices with sysfs attr containing only spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [PATCH 2/2] dm-raid1: [PATCH RFC] dm-raid1: keep writing after leg failure -> fix error end io logic if 'keep_log' set for on log failure; add ctr/... comments
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/2] dm-raid1: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/2] dm-raid1: [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: heinzm@xxxxxxxxxx
• [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Ben Collins <ben.c@xxxxxxxxxxxx>
• Re: [PATCH 1/2] Remove duplicate hwtable entry for XtremIO
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH v2] dm crypt: fix deadlock when algo returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt: Fix deadlock when algo returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH 1/3] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH 1/3] dm: log writes target V2
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: thin_check doesn't use data space map to open data mapping tree
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH 2/3] dm: Export function dm_suspend_md()
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH] dm-crypt: Fix deadlock when algo returns -EBUSY
  • From: Ben Collins <ben.c@xxxxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• thin_check doesn't use data space map to open data mapping tree
  • From: "M.H. Tsai" <mingnus@xxxxxxxxx>
• [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Why wipe crypto keys during suspend (was Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation)
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-crypt: Update URLs to new cryptsetup project page.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• LPC2015: File and Storage Systems uconf
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH RFC] dm-raid1: keep writing after leg failure
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• dm-thin: delete device could take lots of time
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• Re: [PATCH 6/7] block/partitions: use block_device name vsprintf helper
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: [PATCH 1/7] lib/vsprintf: add %*pg format specifier
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: [PATCH 1/7] lib/vsprintf: add %*pg format specifier
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH 1/7] lib/vsprintf: add %*pg format specifier
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [RFC] [PATCH 0/7] fs: add blkdev name format specifier
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 1/7] lib/vsprintf: add %*pg format specifier
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 2/7] fs: use gendisk->disk_name where possible
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 3/7] block: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 4/7] fs: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [RFC] [PATCH 0/7] fs: add blkdev name format specifier
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 5/7] md: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 7/7] drivers: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 6/7] block/partitions: use block_device name vsprintf helper
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: [PATCH 2/2] lib/lcm.c: lcm(n, 0)=lcm(0, n) is 0, not n
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] block: fix blk_stack_limits() regression due to lcm() change
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH 0/7] drivers: Use bool function return values true/false not 1/0
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] block: fix blk_stack_limits() regression due to lcm() change
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A path to a different device was added to an existing mapth
  • From: guy keren <guy.keren@xxxxxxxxxxxxx>
• [PATCH 2/2] Merge Dell MD3XXX hardware table entries
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/2] Remove duplicate hwtable entry for XtremIO
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 30/78] Update hwtable for EMC XtremIO
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 00/78] SUSE SLES resync
  • From: Hannes Reinecke <hare@xxxxxxx>
• multipath: DELL MD3000/MD3000i and MD32xx/MD32xxi regex too broad
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 30/78] Update hwtable for EMC XtremIO
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 00/78] SUSE SLES resync
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 2/2] lib/lcm.c: lcm(n, 0)=lcm(0, n) is 0, not n
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A path to a different device was added to an existing mapth
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH 26/78] 11-dm-mpath.rules: Import blkid values if all paths are down
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 26/78] 11-dm-mpath.rules: Import blkid values if all paths are down
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 77/78] multipathd: asynchronous configuration
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 78/78] multipathd: trigger all devices on startup
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 68/78] libmultipath: unset 'uid_attribute' on failure
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 50/78] Allow zero-sized devices during configuration
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 78/78] multipathd: trigger all devices on startup
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 77/78] multipathd: asynchronous configuration
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 75/78] Push down vector lock during uevent processing
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 74/78] Allow specific CLI commands to run unlocked
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 73/78] multipathd: push down lock in checkerloop()
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 68/78] libmultipath: unset 'uid_attribute' on failure
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 50/78] Allow zero-sized devices during configuration
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 26/78] 11-dm-mpath.rules: Import blkid values if all paths are down
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [git pull] device mapper fix for 4.0-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 43/78] Fixup device-mapper 'cookie' handling
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 3/3] fstests: btrfs balance with dm log writes test
  • From: Filipe David Manana <fdmanana@xxxxxxxxx>
• Re: [PATCH 43/78] Fixup device-mapper 'cookie' handling
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 43/78] Fixup device-mapper 'cookie' handling
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target V2
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 11/12] fs: don't reassign dirty inodes to default_backing_dev_info
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 11/12] fs: don't reassign dirty inodes to default_backing_dev_info
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH] dm-multipath: fix get_word return value when the last word is found
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target V2
  • From: Zach Brown <zab@xxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 11/12] fs: don't reassign dirty inodes to default_backing_dev_info
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.0-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/3] dm: log writes target V2
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: A path to a different device was added to an existing mapth
  • From: Ilan Steinberg <ilan.steinberg@xxxxxxxxxxxxx>
• A path to a different device was added to an existing mapth
  • From: Ilan Steinberg <ilan.steinberg@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] dm: log writes target
  • From: Zach Brown <zab@xxxxxxxxxx>
• Re: [PATCHv3] dm-verity: Add error handling modes for corrupted blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• [PATCH 2/3] fstests: add dm-log-writes test and supporting code
  • From: Josef Bacik <jbacik@xxxxxx>
• [PATCH 1/3] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• [PATCH 3/3] fstests: btrfs balance with dm log writes test
  • From: Josef Bacik <jbacik@xxxxxx>
• [PATCH 0/3] Device mapper log writes patches
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: dm thin: How to shrink think pool device?
  • From: Maxim Patlasov <mpatlasov@xxxxxxxxxxxxx>
• Re: dm thin: How to shrink think pool device?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm thin: How to shrink think pool device?
  • From: Maxim Patlasov <mpatlasov@xxxxxxxxxxxxx>
• Re: dm log userspace: use mempool_create_kmalloc_pool()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCHv3] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCHv2] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH] dm delay: use msecs_to_jiffies for time conversion
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: "Wilck, Martin" <martin.wilck@xxxxxxxxxxxxxx>
• Re: [PATCHv2] dm-verity: Add error handling modes for corrupted blocks
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCHv2] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Will Drewry <wad@xxxxxxxxxxxx>
• [PATCH] dm-verity: Add error handling modes for corrupted blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH 52/78] multipathd: Issue warning on CLI command timeout
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 28/78] multipathd: handle DOMAP_RETRY
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 77/78] multipathd: asynchronous configuration
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 33/78] Do not treat 'transport-offline' paths as 'offline'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 07/78] libmultipath: Skip paths with empty wwid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 29/78] multipathd: cleanup foreground operation
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 74/78] Allow specific CLI commands to run unlocked
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 44/78] multipath: do not print state 'orphan' for option '-l'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 53/78] Use strlen() when checking for valid wwid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 76/78] multipathd: timeout CLI commands when waiting for lock
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 00/78] SUSE SLES resync
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 27/78] kpartx.rules: Skip kpartx for multipath events
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 75/78] Push down vector lock during uevent processing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 21/78] Remove trailing linefeed from sysfs attributes
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 50/78] Allow zero-sized devices during configuration
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 60/78] multipathd: use local variable for watchdog configuration
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 20/78] Make checker_put() and prio_put() idempotent
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 62/78] Skip USB devices during discovery
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 02/78] mpath_persist: Do not call exit() from a shared library
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 03/78] libmultipath: filter for missing property in get_refwwid()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 72/78] libmultipath: make vpd page 0x80 optional
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 10/78] Fixup multipathd.socket to resolve ordering dependeny
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 55/78] uxlsnr: use typedef for trigger function
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 42/78] Remove last argument from verify_paths()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 35/78] Separate out uevent parsing functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 58/78] Remove dm_udev_XXX wrapper functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 69/78] Separate out vpd parsing functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 64/78] Assign local priority for NAA VPD descriptor
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 54/78] multipathd: Use standard lists for CLI handling
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 68/78] libmultipath: unset 'uid_attribute' on failure
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 47/78] Do not print empty multipaths section
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 37/78] mpath_persist: cleanup
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 51/78] Rework uev_add_path()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 01/78] libmultipath: remove compilation warning in devmapper.c
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 43/78] Fixup device-mapper 'cookie' handling
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 73/78] multipathd: push down lock in checkerloop()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 71/78] Do not automatically fall back to vpd uid generation
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 34/78] Check for valid DM_DEVICE_INFO before proceeding
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 63/78] Read wwid from sysfs vpg_pg83 attribute
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 66/78] Update multipath.conf.5 to clarify wwid generation
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 78/78] multipathd: trigger all devices on startup
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 65/78] Use sysfs attribute vpd_pg80 to read serial number
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 57/78] multipath: enable sync support
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 15/78] Use 'SCSI_IDENT_.*' as the default property whitelist
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 05/78] discovery: do not fail discovery on individual devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 40/78] Remove sysfs_get_dev
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 18/78] Disable reassign maps per default
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 11/78] Fixup dependencies in multipathd.service
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 46/78] Implement 'uxsock_timeout' keyword
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 31/78] multipath: check for running daemon when called with '-u'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 06/78] libmultipath: Prefer deprecated 'getuid' callout
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 56/78] multipathd: lock cli client list
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 32/78] Revert 'return PATH_DOWN for quiesced paths'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 59/78] Revert to ACT_RELOAD in domap if the map exists
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 04/78] Double uevent stacksize yet again
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 36/78] Use poll() when receiving uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 48/78] multipathd: reload map if reinstate failed
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 61/78] Ignore devices when sysfs_get_tgt_nodename fails
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 39/78] multipath: Use standard 'major' macro
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 45/78] Return error when receiving CLI packet
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 19/78] multipathd: implement 'list path <path>' cli command
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 09/78] Add multipath rules for systemd support
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 49/78] multipathd: do not remove paths without uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 14/78] kpartx.rules: do not call blkid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 22/78] multipath: implement option '-u' for uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 67/78] libmultipath: Fall back to SG_IO if no UID could be assigned
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 26/78] 11-dm-mpath.rules: Import blkid values if all paths are down
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 13/78] Do not print empty device strings during discovery
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 16/78] Fixup wwid blacklist printing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 12/78] multipathd: set correct PID when running in debug mode
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 17/78] Allow for empty path argument when printing information
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 25/78] multipath.rules: fixup race condition with systemd
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 30/78] Update hwtable for EMC XtremIO
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 23/78] Install multipath rule under '56-multipath.rules'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 08/78] Make systemd installation path configurable
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 24/78] multipath.rules: Whitelist devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 70/78] multipathd: use SG_IO as fallback to generate uid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 41/78] Add paths with a size of '0' as 'ghost' paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 38/78] kpartx: use standard 'major' and 'minor' macros
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm log userspace: base: fix compile warning
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• [PATCH] dm log userspace: transfer: match wait_for_completion_timeout return type
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• Re: [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/3] libmultipath: only add uninitialized paths in check_path
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/3] Add find_multipaths to multipath.conf man page
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/3] add find_multipaths option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 0/7] dm: add full blk-mq support to request-based DM
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• [PATCH 2/7 v3] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7 v3] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/7 v2] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 1/7 v2] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 2/7] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• [PATCH 2/7 v2] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7 v2] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• [PATCH 6/7] dm: optimize dm_mq_queue_rq to _not_ use kthread if using pure blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/7] dm: add 'use_blk_mq' module param and expose in per-device ro sysfs attr
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/7] dm: add full blk-mq support to request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/7] blk-mq: don't wait in blk_mq_queue_enter() if __GFP_WAIT isn't set
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/7] dm: add full blk-mq support to request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/7] blk-mq: export blk_mq_run_hw_queues
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/7] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm log userspace: use mempool_create_kmalloc_pool()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: [PATCH 00/15] Multipath patch resync
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• [PATCH] Update ETERNUS DX entry
  • From: Gerhard Wichert <Gerhard.Wichert@xxxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 00/15] Multipath patch resync
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH 05/15] multipathd: fix memory corruption issue
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 15/15] libmultipath: autodetect ALUA CLARiiON configurations
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 02/15] libmultipath: fix sysfs_get_size bug
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 01/15] correctly set partition delimiter on rename
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 11/15] multipath: enable configuration directory
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 00/15] Multipath patch resync
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 06/15] multipathd: add deferred_remove support
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 03/15] Revert "libmultipath: fixup strlcpy"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 07/15] multipathd: don't buffer output with systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 04/15] libmultipath: refactor partmaps code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 13/15] multipathd: Add delayed path reintegration
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 12/15] libmultipath: cleanup parser code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 08/15] libmutipath: allow blanks in device blacklist
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 09/15] multipathd: read-only bindings
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 14/15] Fix doublee free of alias after map add failure
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [patch] dm log userspace: use mempool_create_kmalloc_pool()
  • From: David Rientjes <rientjes@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: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH 8/8 v2] dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm-cache metadata memory footprint
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/8] dm: remove request-based DM queue's lld_busy_fn hook
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/8] dm sysfs: introduce ability to add writable attributes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/8] dm: remove request-based logic from make_request_fn wrapper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 8/8] dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/8] dm: only run the queue on completion if congested or no requests pending
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/8] dm: remove unnecessary wrapper around blk_lld_busy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/8] dm: don't schedule delayed run of the queue if nothing to do
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/8] dm: optimize request-based queue processing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Spelic <spelic@xxxxxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Laurence Oberman <loberman@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Laurence Oberman <loberman@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/4] dm-latency: add I/O latency measurement in device mapper
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 1/4] dm-latency: move struct mapped_device from dm.c to dm.h
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 4/4] dm-latency: add reset function to dm-latency in sysfs interface
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 3/4] dm-latency: add sysfs interface
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 0/4] dm-latency: Introduction
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: "Busch, Keith" <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: FIXED! [was: awful request merge results while simulating high IOPS] multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• FIXED! [was: awful request merge results while simulating high IOPS] multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 4/4] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 3/4] dm: remove request-based logic from make_request_fn wrapper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [RFC PATCH 4/4] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/4] dm: remove request-based DM queue's lld_busy_fn hook
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/4] dm: remove unnecessary wrapper around blk_lld_busy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/4] dm: simplify request-based DM a bit and an RFC-like perf tweak
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: System freeze for few seconds when using dm-cache on high load
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [git pull] additional device mapper changes for 3.20
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Performance testing of related dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Performance testing of related dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-snapshot: fix a possible invalid memory access on unload
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: fix a race condition in dm_get_md
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• dm-cache metadata memory footprint
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• targeting dm-crypt cpu scalability changes for 3.20 still [was: Re: [git pull] device mapper changes for 3.16]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 6/7] dm-crypt: make it possible to disable offload to thread
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/7] dm-crypt: remove io_pool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 7/7] dm-crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH v2] dm-io: reject unsupported DISCARD requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 3/3] md bitmap: export bitmap_destroy() to support dm-raid down takover to raid0
  • From: heinzm@xxxxxxxxxx
• [PATCH 2/3] md raid0: access mddev->queue (request queue member) conditionally because it is not set when accessed from dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/3] md core: add 2 API functions for takeover and resize to support dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: heinzm@xxxxxxxxxx
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/7] dm-crypt: sort writes
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/7] dm-crypt: make it possible to disable offload to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/7] dm-crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/7] dm-crypt: remove io_pool
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATH 2/7] dm-crypt: don't allocate pages for a partial request.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/7] dm-crypt: use unbound workqueue for request processing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [git pull] device mapper changes for 3.20
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm space map disk: fix sm_disk_count_is_more_than_one()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm log userspace: split flush_entry_pool to be per dirty-log [was: Re: mempool.c: Replace io_schedule_timeout with io_schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2 3/3] dm: Get devices using name_to_dev_t
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 2/3] init: Stricter checking of major:minor root= values
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Re: [PATCH RFCv2 05/10] dm-dedup: COW B-tree backend
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 05/10] dm-dedup: COW B-tree backend
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: [PATCH] sched: call blk_schedule_flush_plug from io_schedule
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] dm: Get devices using name_to_dev_t
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] sched: call blk_schedule_flush_plug from io_schedule
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• blk-mq crash with dm-multipath in for-3.20/core
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache: Promote-Demote Policy. How it works ?
  • From: "BK, GirishKumar" <GirishKumar.BK@xxxxxxxxxx>
• Re: dm-dedup can not make module
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] block: do not merge two requests with sg gaps if unsupported
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-dedup can not make module
  • From: Zhichao Cao <caozhichao91@xxxxxxxxx>
• Re: [PATCH v2] block: do not merge two requests with sg gaps if unsupported
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFCv2 03/10] dm-dedup: hash computation
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: dmcache RAID1 bug?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH RFCv2 10/10] dm-dedup: documentation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] dm snapshot: Deletion of unnecessary checks before the function call "vfree"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dm create error
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH] Remove might_sleep from wait_event_cmd
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md:Remove unneeded fixme comment for the function, pool_ctr
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH RFCv2 10/10] dm-dedup: documentation
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <Anand.Jain@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <Anand.Jain@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] last couple device mapper fixes for 3.19 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [PATCH 1/2] init: Stricter checking of major:minor root= values
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 2/2] dm: Get devices using name_to_dev_t
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf-pc] [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• Re: [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: DM-Delay
  • From: "BK, GirishKumar" <GirishKumar.BK@xxxxxxxxxx>
• [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm create error
  • From: Xiaoqiang Zhou <zhouxiaoqiang.mstech@xxxxxxxxx>
• Re: [Lsf-pc] [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: "suresh.babu.kandukuru@xxxxxxxxxx" <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• dm_mirror/dm_raid1 limitations ?.
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• [PATCH] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [git pull] a few additional device mapper fixes for 3.19 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: Respect request queue page gaps flag
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: Some thoughts about providing data block checksumming for ext4
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: dm-cache - should origin device and cache be identical when quiescent?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• A couple of questions related to dm-thin in linux-3.19-rc5
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• dm-cache - should origin device and cache be identical when quiescent?
  • From: Alex Sudakar <alex.sudakar@xxxxxxxxx>
• Re: DM-Delay
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• DM-Delay
  • From: Sourav Basu <sourav.juit@xxxxxxxxx>
• Re: livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 7/8] multipathd: don't buffer output with systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/8] Revert "libmultipath: fixup strlcpy"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 4/8] libmultipath: refactor partmaps code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/8] libmultipath: fix sysfs_get_size bug
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/8] Misc multipath patches.
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 6/8] multipathd: add deferred_remove support
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/8] correctly set partition delimiter on rename
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 5/8] multipathd: fix memory corruption issue
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 8/8] libmutipath: allow blanks in device blacklist
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm: Get devices using name_to_dev_t
  • From: Daniel Ehrenberg <dehrenberg@xxxxxxxxxx>