Linux Device-Mapper Development

• Thread Index

• Re: [PATCH v5 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] device mapper support for strace
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] device mapper support for strace
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/1] device-mapper: Do not override error code from dm_get_device()
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• lvconvert leaves devices unsynced and unpolled?
  • From: Greg Stark <stark@xxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• Re: kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Unnecessary snapshot validation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Unnecessary snapshot validation
  • From: Frederick Grose <fgrose@xxxxxxxxx>
• Re: kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.2-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• Re: [PATCH v2 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• AMD-Vi IO_PAGE_FAULTs and ata3.00: failed command: READ FPDMA QUEUED errors since Linux 4.0
  • From: Andreas Hartmann <andihartmann@xxxxxxxxxxxxxxx>
• DMCache Desing Questions
  • From: Leonardo Santos <heiligerstein@xxxxxxxxx>
• Re: [PATCH v2 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: dm cache: fix alloc_bitset check that always evaluates as false
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: crypt: update wiki page URL
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-4.2-rc4/drivers/md/dm-cache-policy-smq.c:1689: bad if test ?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipathd removing DM devices that don't belong to it
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: multipathd removing DM devices that don't belong to it
  • From: Artem Danielov <artem@xxxxxxxxxxxx>
• linux-4.2-rc4/drivers/md/dm-cache-policy-smq.c:1689: bad if test ?
  • From: David Binderman <dcb314@xxxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] dm: crypt: update wiki page URL
  • From: Baruch Siach <baruch@xxxxxxxxxx>
• [PATCH] dm cache: fix alloc_bitset check that always evaluates as false
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [RFC PATCH] block: dm thin: export how block device handles -ENOSPC
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• DM dtr activation context
  • From: <gilib123@xxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: DM-Cache Writeback & Direct IO?
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: back-ported dm-cache not forwarding read-ahead bios to origin
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• [PATCH 2/2] multipathd: Disabled code that is not being used.
  • From: Tejaswini Poluri <tpoluri@xxxxxxxxxx>
• [PATCH 1/2] multipathd: Fixing add map functionality
  • From: Tejaswini Poluri <tpoluri@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] md:Check if call to thaw_bdev fails in unlock_fs
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: back-ported dm-cache not forwarding read-ahead bios to origin
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• back-ported dm-cache not forwarding read-ahead bios to origin
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• add a bi_error field to struct bio V3
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [git pull] device mapper fixes for 4.2-rc3
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [dm:for-next 7/7] drivers/md/dm-cache-target.c:3585:37: error: 'pool' undeclared
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [dm:for-next 7/7] drivers/md/dm-cache-target.c:3585:37: error: 'pool' undeclared
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: dm-mpath: always return reservation conflict
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] dm-mpath: always return reservation conflict
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH] dm-mpath: always return reservation conflict
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [patch] mm: improve __GFP_NORETRY comment based on implementation
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5 00/11] simplify block layer based on immutable biovecs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: fix a crash due to incorrect cleanup sequence
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: reinstate path not working
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH] multipathd: add map feature fix
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: DM-Cache Writeback & Direct IO?
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: DM-Cache Writeback & Direct IO?
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: DM-Cache Writeback & Direct IO?
  • From: Leonardo Santos <heiligerstein@xxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: API for multi-segment atomic IO
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: DM-Cache Writeback & Direct IO?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: 4.1: 9a0e609e3fd ("dm: only run the queue on completion if ....") causes significant overhead in osq_lock on ext4/multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• DM-Cache Writeback & Direct IO?
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• 4.1: 9a0e609e3fd ("dm: only run the queue on completion if ....") causes significant overhead in osq_lock on ext4/multipath
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Gili B <gilib123@xxxxxxxxxxx>
• API for multi-segment atomic IO
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 7/7] dm: make dm_vcalloc use kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/7] dm: use kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/7] dm-thin: use kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/7] dm-stats: use kvmalloc_node
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/7] dm-ioctl: join flags DM_PARAMS_KMALLOC and DM_PARAMS_VMALLOC
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/7] mm/vmalloc: export __vmalloc_node_flags
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/7] mm: reliable memory allocation with kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: crypt: update wiki page URL
  • From: Baruch Siach <baruch@xxxxxxxxxx>
• Re: [PATCH v2 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH] kpartx: use inode to identify loopback mounts
  • From: Risto Kankkunen <risto.kankkunen@xxxxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Re: Integrating new DM targets to LVM
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Re: [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: reinstate path not working
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/2] Couple of minor code cleanups
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH 1/2] Remove unused parameter in btree_split_sibling()
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH 2/2] dm-btree-remove: Remove function get_nr_entries()
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 5/7] dm-thin: use dm_kvmalloc
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: Integrating new DM targets to LVM
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Re: Getting mapped device namw
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Getting mapped device namw
  • From: Gili B <gilib123@xxxxxxxxxxx>
• [PATCH v5 08/11] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH v5 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Integrating new DM targets to LVM
  • From: Gili B <gilib123@xxxxxxxxxxx>
• [PATCH 7/7] dm: make dm_vcalloc use dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/7] dm-stats: use dm_kvmalloc_node
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/7] dm-thin: use dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/7] dm: introduce dm_kvmalloc
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/7] dm-stats: rename functions
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/7] mm/vmalloc: export __vmalloc_node_flags
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/7] reliable memory allocation and fix for bug 1225370
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/7] dm-ioctl: join flags DM_PARAMS_KMALLOC and DM_PARAMS_VMALLOC
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• thin metadata raw backup
  • From: Ilya Basin <basinilya@xxxxxxxxx>
• [PATCH] dm: test return value for DM_MAPIO_SUBMITTED
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [RFC PATCH] bio integrity: do not assume bio_integrity_pool exists if bioset exists
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: DM_CACHE_SMQ is experimental and enabled by default? (was: Re: dm cache: add stochastic-multi-queue (smq) policy)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: [PATCH 3.10, 3.14] dm snapshot: allocate a per-target structure for snapshot-origin target
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: reinstate path not working
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [GIT PULL] Core block IO bits for 4.2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [lvm-devel] udev cookie on DM_DEVICE_RELOAD
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: udev cookie on DM_DEVICE_RELOAD
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Device Mapper Persistent Configuration
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: udev cookie on DM_DEVICE_RELOAD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• udev cookie on DM_DEVICE_RELOAD
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm verity: remove unused mempool
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: Device Mapper Persistent Configuration
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Re: Device Mapper Persistent Configuration
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Device Mapper Persistent Configuration
  • From: Gili B <gilib123@xxxxxxxxxxx>
• Stochastic-Multi-Queue Performance
  • From: Leonardo Santos <heiligerstein@xxxxxxxxx>
• [PATCH] Fixing the find_loop_by_file function to properly compare the filename by respecting the LO_NAME_SIZE.
  • From: Jorge Niedbalski <jorge.niedbalski@xxxxxxxxxxxxx>
• Re: DM_CACHE_SMQ is experimental and enabled by default? (was: Re: dm cache: add stochastic-multi-queue (smq) policy)
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.2-rc1
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-dedup: freeze and panic
  • From: Vincent Donnefort <vdonnefort@xxxxxxxxx>
• Re: [GIT PULL] Core block IO bits for 4.2
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: [GIT PULL] Core block IO bits for 4.2
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] Core block IO bits for 4.2
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: reinstate path not working
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: 40% performance loss with multipath since kernel 3.12
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• 40% performance loss with multipath since kernel 3.12
  • From: Derick Swanepoel <dswanepoel@xxxxxxxxx>
• [git pull] device mapper changes for 4.2
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: General protection fault with ext4 - LVM - raid456 (Raid 6)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: failed command: WRITE FPDMA QUEUED, suspiciously on two different disks
  • From: Sami Farin <hvtaifwkbgefbaei@xxxxxxxxx>
• General protection fault with ext4 - LVM - raid456 (Raid 6)
  • From: Jouni Karvo <Jouni.Karvo@xxxxxx>
• Re: Persistent memory interface
  • From: "hch@xxxxxx" <hch@xxxxxx>
• Re: reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Persistent memory interface
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: Persistent memory interface
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• possible bug with kpartx -d and absolute paths
  • From: Parke <parke.nexus@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH] fs/block_dev.c: Remove WARN_ON() when inode writeback fails
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] fs/block_dev.c: Remove WARN_ON() when inode writeback fails
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: Persistent memory interface
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: multipathd removing DM devices that don't belong to it
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: 3.12.y: srcu warning during free_dev() with dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 3.12.y: srcu warning during free_dev() with dm-multipath
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: 3.12.y: srcu warning during free_dev() with dm-multipath
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: 3.12.y: srcu warning during free_dev() with dm-multipath
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• [PATCH v2 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH v2 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• [PATCH v2 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH v2 2/3] dm: Export function dm_suspend_md()
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: Persistent memory interface
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: Unnecessary snapshot validation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Persistent memory interface
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Persistent memory interface
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Persistent memory interface
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: Persistent memory interface
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Persistent memory interface
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• WARNING: at fs/block_dev.c:5 when removing LV on removed device
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• 3.12.y: srcu warning during free_dev() with dm-multipath
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• [dm:for-next 43/47] drivers/md/dm-cache-policy-smq.c:1751:36: error: redefinition of 'smq_policy_type'
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/4] Integrate dm-latency functionality to dm-statistics
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• multipathd removing DM devices that don't belong to it
  • From: Artem Danielov <artem@xxxxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: [PATCH 3/4] dm stats: report histogram of latencies
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 0/4] Integrate dm-latency functionality to dm-statistics
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: [PATCH 3/4] dm stats: report histogram of latencies
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Minfei Huang <mnfhuang@xxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Minfei Huang <mnfhuang@xxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH] dm-statistics: update documentation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Newbie device mapper questions
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Newbie device mapper questions
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: dmsetup remove gives EBUSY (even though it shouldn't be busy)
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: [PATCH 3/4] dm stats: report histogram of latencies
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/4] dm stats: report histogram of latencies
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/4] Integrate dm-latency functionality to dm-statistics
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/4] dm stats: report histogram of latencies
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: [PATCH 0/4] Integrate dm-latency functionality to dm-statistics
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Ewan Milne <emilne@xxxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Ewan Milne <emilne@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC] add a bi_error field
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [RFC] add a bi_error field
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [RFC] add a bi_error field
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• add a bi_error field to struct bio V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC] add a bi_error field
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: anup modak <amodak2014@xxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/4] dm stats: support precise timestamps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: ALUA - rescan device capacity on zero sized block devices
  • From: Ewan Milne <emilne@xxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Trying to us dmcache with zram block device
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• device-mapper-1.02.67]
  • From: "Finneran, Gary" <gary.finneran@xxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/4] dm stats: support statistics on requests-based devices
  • From: Laurence Oberman <loberman@xxxxxxxxxx>
• [PATCH 4/4] dm stats: support statistics on requests-based devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/4] dm stats: report histogram of latencies
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/4] Integrate dm-latency functionality to dm-statistics
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/4] dm stats: support precise timestamps
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/4] dm-statistics: better argument validation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH 8/8] cfq-iosched: charge async IOs to the appropriate blkcg's instead of the root
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 8/8] cfq-iosched: charge async IOs to the appropriate blkcg's instead of the root
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH 1/4] Add libmpathcmd library and use it internally
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/4] add raw format multipathd commands
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 4/4] Make use of /run depend on systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/4] libmultipath: add ignore_new_boot_devs option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/4] misc multipath patches
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-statistics: better argument validation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-statistics: better argument validation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: block: add a bi_error field to struct bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] block: add a bi_error field to struct bio
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 03/10] multipathd: use /run instead of /var/run
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• [PATCH 3.10, 3.14] dm snapshot: suspend merging snapshot when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3.10] add dm_internal_suspend and dm_internal_resume
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3.14] dm snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3.10] dm snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] block: add a bi_error field to struct bio
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3.10, 3.14] dm snapshot: allocate a per-target structure for snapshot-origin target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [RFC] add a bi_error field
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] libmultipath: don't lock block device but use lock files
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Next release plans?
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Next release plans?
  • From: Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] libmultipath: don't lock block device but use lock files
  • From: Christian Seiler <christian@xxxxxxxx>
• Re: Poor snapshot performance in linux-3.19
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• [PATCH 19/98] dm-log-userspace.h: use __u32, __s32 and __u64 from linux/types.h
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• [git pull] device mapper fixes for 4.1-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Poor snapshot performance in linux-3.19
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Correct way to resize a device
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH] dm: fix reload failure of 0 path multipath mapping on blk-mq devices
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• [dm:dm-4.1-for-ejt 33/33] drivers/md/dm-thin.c:1543:25: error: 'BIO_CHAIN' undeclared
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: dm: fix false alarm in free_rq_clone() for non blk-mq target
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: dm: fix false alarm in free_rq_clone() for non blk-mq target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Poor snapshot performance in linux-3.19
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• Re: dm: fix false alarm in free_rq_clone() for non blk-mq target
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: dm: fix false alarm in free_rq_clone() for non blk-mq target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm:dm-4.1-for-ejt 33/33] drivers/md/dm-thin.c:1543:25: error: 'BIO_CHAIN' undeclared
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Question about suspending a device
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: Poor snapshot performance in linux-3.19
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Poor snapshot performance in linux-3.19
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH] dm: fix false alarm in free_rq_clone() for non blk-mq target
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH] dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for 4.1-rc] dm: run queue on re-queue
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for 4.1-rc] dm: run queue on re-queue
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Alex Elder <elder@xxxxxxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dmsetup remove gives EBUSY (even though it shouldn't be busy)
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Proposal for annotating _unstable_ pages
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v4 08/11] block: kill merge_bvec_fn() completely
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v4 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: NeilBrown <neilb@xxxxxxx>
• dmsetup remove gives EBUSY (even though it shouldn't be busy)
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: [PATCH 6/4 v2] dm-raid: enhance discard_zeroes_data documentation
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] libmultipath: don't lock block device but use lock files
  • From: Christian Seiler <christian@xxxxxxxx>
• Re: [PATCH] libmultipath: don't lock block device but use lock files
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] libmultipath: don't lock block device but use lock files
  • From: Christian Seiler <christian@xxxxxxxx>
• [PATCH dm] dm thin: __blkdev_issue_discard_async() can be static
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [dm:for-next 30/30] drivers/md/dm-thin.c:338:5: sparse: symbol '__blkdev_issue_discard_async' was not declared. Should it be static?
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [PATCH 1/1] scsi: add Synology to 1024 sector blacklist
  • From: michaelc@xxxxxxxxxxx
• Re: Proposal for annotating _unstable_ pages
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH for-4.2 3/3] block: remove export for blk_queue_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 1/3] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Proposal for annotating _unstable_ pages
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: Proposal for annotating _unstable_ pages
  • From: Jan Kara <jack@xxxxxxx>
• Re: Proposal for annotating _unstable_ pages
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Regarding RHEL multipath-tools-0.5.0
  • From: "Nalla, Ravikanth" <ravikanth.nalla@xxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Let's get a File & Storage miniconf going at LPC2015!
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH v2 RESEND] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: Let's get a File & Storage miniconf going at LPC2015!
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Regarding the correct version of sysfs util for multipath-tools-0.4.5
  • From: Ravikanth Nalla <ravikanth.nalla@xxxxxxxxx>
• Re: [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 v2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH for-4.2 v2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2 RESEND] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH v2 RESEND] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH for-4.2 v2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: reinstate path not working
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 06/14] dm: rename methods that requeue requests
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Jan Kara <jack@xxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Possible BUG in the entry removal process of dm-btree structure
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Brandon Smith <freedom@xxxxxxxxxxxxxxx>
• reinstate path not working
  • From: Tejaswini Poluri <tejaswinipoluri3@xxxxxxxxx>
• Re: [PATCH for-4.2 06/14] dm: rename methods that requeue requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm-raid1: keep writing after leg failure
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• Re: dm-raid1: keep writing after leg failure
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• Re: multipath-tools git repository is unavailable
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxxxxxx>
• Re: [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Jan Kara <jack@xxxxxxx>
• Possible BUG in the entry removal process of dm-btree structure
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• [PATCH 08/10] Fix issues with user_friendly_names initramfs bindings
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 02/10] fix memory leaks on realloc failures
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 10/10] resize reply buffer for mutipathd help message
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 01/10] libmultipath: Add prioritizer context data
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 05/10] update multipath rules to deal with partition devices
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 04/10] retrigger uevents to try and get the uid through udev
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 06/10] change order of multipath.rules
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 00/10] Multipath path resync
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 03/10] multipathd: use /run instead of /var/run
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 07/10] make kpartx -d remove all partitions
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 09/10] Make multipath deactivate devices before iscsi shutdown
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm crypt: Add comments to better describe crypto processing logic.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• [PATCH 6/4 v2] dm-raid: enhance discard_zeroes_data documentation
  • From: heinzm@xxxxxxxxxx
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: dm-raid1: keep writing after leg failure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm crypt: Add comments to better describe crypto processing logic.
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• [PATCH v2 5/4] dm-raid: add merge method to target
  • From: heinzm@xxxxxxxxxx
• Re: snapshot-origin freezes system - what am I doing wrong?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• snapshot-origin freezes system - what am I doing wrong?
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• [PATCH 1/2] Increase number of retries
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• [PATCH 2/2] Display error when we fail to delete device
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• [PATCH for-4.2 03/14] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 06/14] dm: rename methods that requeue requests
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 11/14] dm thin: range discard support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 05/14] dm: do not allocate any mempools for blk-mq request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 08/14] dm btree: add dm_btree_remove_leaves()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 12/14] dm thin: cleanup overwrite's endio restore to be centralized
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 04/14] block: factor out blkdev_issue_discard_async
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 13/14] dm thin: cleanup schedule_zero() to read more logically
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 09/14] dm thin metadata: add dm_thin_find_mapped_range()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 10/14] dm thin metadata: add dm_thin_remove_range()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 14/14] dm thin metadata: remove in-core 'read_only' flag
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 07/14] dm: factor out a common cleanup_mapped_device()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 01/14] block: remove management of bi_remaining when restoring original bi_end_io
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 02/14] block: remove export for blk_queue_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-4.2 00/14] block, dm: first batch of changes for 4.2
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-next dm-thinp regression due to "bio: skip atomic inc/dec of ->bi_remaining for non-chains"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-next dm-thinp regression due to "bio: skip atomic inc/dec of ->bi_remaining for non-chains"
  • From: Jan Kara <jack@xxxxxxx>
• Re: linux-next dm-thinp regression due to "bio: skip atomic inc/dec of ->bi_remaining for non-chains"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-next dm-thinp regression due to "bio: skip atomic inc/dec of ->bi_remaining for non-chains"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• linux-next dm-thinp regression due to "bio: skip atomic inc/dec of ->bi_remaining for non-chains"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-raid1: keep writing after leg failure
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• dm-writeboost v1.0.0 released
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH] dm-raid1: keep writing after leg failure
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• Re: [PATCH 0/3] [RESEND]dm-raid1: several fixes about writing on out of sync mirror device
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• multipath-tools git repository is unavailable
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Writes going to source device in write-back mode
  • From: "BK, GirishKumar" <GirishKumar.BK@xxxxxxxxxx>
• Re: dm-raid: unsynced raid snapshot creation/deletion causes panic (work queue teardown race)
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: dm-raid: unsynced raid snapshot creation/deletion causes panic (work queue teardown race)
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] [RESEND]dm-raid1: several fixes about writing on out of sync mirror device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] block: remove export for blk_queue_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 08/17] scsi_dh_alua: Make stpg synchronous
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 08/17] scsi_dh_alua: Make stpg synchronous
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 08/17] scsi_dh_alua: Make stpg synchronous
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 08/17] scsi_dh_alua: Make stpg synchronous
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dm-snap-persistent: chunk_io doesn't call destroy_work_on_stack in 3.10.76
  • From: Minfei Huang <minfei.huang@xxxxxxxxxxx>
• [git pull] device mapper fixes for 4.1-rc3
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 3/4] Documentation: add version history entries for raid0 support _and_ forgotten devices_handle_discards_safely module paramater
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH v2 2/4] md-raid0: conditional mddev->queue access to suit dm-raid
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH v2 4/4] dm-raid: remove bogus parse_raid_params() comment about devices_handle_discards_safely
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH v2 3/4] Documentation: add version history entries for raid0 support _and_ forgotten devices_handle_discards_safely module paramater
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH v2 2/4] md-raid0: conditional mddev->queue access to suit dm-raid
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH v2 1/4] dm-raid: Add support for the MD RAID0 personality
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• dm-snap-persistent: chunk_io doesn't call destroy_work_on_stack in 3.10.76
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH v2] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Dumb question; please help
  • From: Frederick Grose <fgrose@xxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: Dumb question; please help
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Dumb question; please help
  • From: Locane <locane@xxxxxxxxx>
• [PATCH v3 08/11] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH v3 01/11] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Trouble with ALUA on controller failover
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH] Revert "dm crypt: fix deadlock when async crypto algorithm returns -EBUSY"
  • From: Horia Geantă <horia.geanta@xxxxxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH] Revert "dm crypt: fix deadlock when async crypto algorithm returns -EBUSY"
  • From: Rabin Vincent <rabin.vincent@xxxxxxxx>
• Re: [PATCH 01/10] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: Yu Chen <yu.c.chen@xxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 01/10] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 01/10] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: 4.1-rc2 dm-multipath-mq kernel warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A target for hotswap?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• 4.1-rc2 dm-multipath-mq kernel warning
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Rabin Vincent <rabin@xxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: Yu Chen <yu.c.chen@xxxxxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Ben Collins <ben.c@xxxxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3.14 73/92] dm crypt: fix deadlock when async crypto algorithm returns -EBUSY
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: A target for hotswap?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [4.1-rc1][Hibernation failed] bisect result included
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• A target for hotswap?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: ppc64le crash in dm on 4.1+
  • From: Joel Stanley <joel@xxxxxxxxx>
• Re: dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Trouble with ALUA on controller failover
  • From: Adam Drew <Adam.Drew@xxxxxxxxxxxxxxxxx>
• Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Abelardo Ricart III <aricart@xxxxxxxxxx>
• Re: dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Aaro Koskinen <aaro.koskinen@xxxxxxxxx>
• Re: Regression: Disk corruption with dm-crypt and kernels >= 4.0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: ppc64le crash in dm on 4.1+
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.1-rc2
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix blk-mq request-based DM queue initialization
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: dm: fix blk-mq request-based DM queue initialization
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dm: fix blk-mq request-based DM queue initialization
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• ppc64le crash in dm on 4.1+
  • From: Joel Stanley <joel@xxxxxxxxx>
• Linux 4.1-rc1: dm crash / regression
  • From: Aaro Koskinen <aaro.koskinen@xxxxxxxxx>
• Re: dm: fix blk-mq request-based DM queue initialization
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Storage Management Job Vacancy at Red Hat
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm: fix free_rq_clone() NULL pointer when requeueing unmapped request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] dm: fix blk-mq request-based DM queue initialization
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH] dm-raid: unsynced raid snapshot creation/deletion causes panic (work queue teardown race)
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 3/4] Documentation: add version history entries for raid0 support _and_ forgotten devices_handle_discards_safely module paramater
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 4/4] dm-raid: remove bogus parse_raid_params() comment about devices_handle_discards_safely
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 1/4] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 2/4] md-raid0: conditional mddev->queue access to suit dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 0/4] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH] dm: fix blk-mq request-based DM queue initialization
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 01/10] block: make generic_make_request handle arbitrarily sized bios
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: Kernel v4.1-rc1 + MQ dm-multipath + MQ SRP oops
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 01/10] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 2/1] dm: do not allocate any mempools for blk-mq request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3] block, dm: don't copy bios for request clones
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/1] dm: do not allocate any mempools for blk-mq request-based DM
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3] block, dm: don't copy bios for request clones
  • From: Christoph Hellwig <hch@xxxxxx>