Linux Device-Mapper Development

• Thread Index

• Re: [PATCH v2] swait: export symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] swait: export symbols __prepare_to_swait and __finish_swait
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] swait: export symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] swait: export symbols __prepare_to_swait and __finish_swait
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2] swait: export symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [patch 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-flakey: corrupt_bio_byte broken since Linux 4.0
  • From: Anton Eliasson <anton.eliasson@xxxxxxxx>
• Re: [patch 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [patch 3/4] dm-writecache
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] multipath-tools: fix help for hds prio
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH] dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Monty Pavel <monty_pavel@xxxxxxxx>
• [dm:for-next 10/13] drivers/md/dm-writecache.c:2301:10: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'int'
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [patch 1/4] x86: optimize memcpy_flushcache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [patch 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 3/4] dm-writecache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 1/4] x86: optimize memcpy_flushcache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 0/4] dm-writecache patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-writecache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: dm-writecache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writecache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: dm-writecache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-writecache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: dm-writecache
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] multipath.conf.5: clarify property whitelist handling
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/2] libmultipath: print correct default for delay_*_checks
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [release] multipath-tools 0.7.7
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] multipath-tools: configure hitachi ams2000 and hus100 as full active arrays
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: fix error parsing "find_multipaths strict"
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] libmultipath: fix error parsing "find_multipaths strict"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [release] multipath-tools 0.7.7
  • From: "Martin Wilck" <Martin.Wilck@xxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Incorrect results for device mapper statistics
  • From: Drew Hastings <dhastings@xxxxxxxxxxxxxxxxxx>
• [PATCH] dm rq: replace BUG_ON(!irqs_disabled) with lockdep's lock annotation
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Pankaj Agarwal <pankaj@xxxxxxxxxxxxxxxxx>
• Re: how to set higher then 128 nr_requests on LV's
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] multipath-tools: configure hitachi ams2000 and hus100 as full active arrays
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH 2/2] multipath-tools: refresh kernel-doc from kernel sources
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH 1/2] multipath-tools: add +x to doc-preclean.pl and split-man.pl
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] Allow the compiler to verify consistency of declarations and definitions
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH] multipath-tools: fix compilation with musl libc
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH v3] multipath-tools: Remove trailing/leading whitespaces and reformat code
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH v2] multipath-tools: replace FSF address with a www pointer
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [release] multipath-tools 0.7.7
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [release] multipath-tools 0.7.7
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [release] multipath-tools 0.7.7
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [git pull] device mapper fixes for 4.17-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH REPOST] dm rq: remove BUG_ON(!irqs_disabled) check
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH REPOST] dm rq: remove BUG_ON(!irqs_disabled) check
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH REPOST] dm rq: remove BUG_ON(!irqs_disabled) check
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [patch 7/8] dm-integrity: flush journal on suspend when using separate device
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 6/8] dm-integrity: use version 2 for separate metadata
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 1/8] dm-integrity: use kvfree
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 2/8] dm-integrity: change the variable suspending from bool to int
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 5/8] dm-integrity: allow external devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 3/8] dm-integrity: report size in the status
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 4/8] dm-integrity: add ic->start in get_data_sector
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 0/8] dm-integrity patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 8/8] dm-integrity: recalculate checksums
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Undo removing a missing PV to a VG, which caused inconsistent metadata
  • From: Patrick Mitchell <patricklmitchell9@xxxxxxxxx>
• Re: dm/raid1: Remove VLA usage
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] dm/raid1: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] fault-injection: reorder config entries
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v5] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v4] fault-injection: introduce kvmalloc fallback options
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH v4] fault-injection: introduce kvmalloc fallback options
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] fault-injection: reorder config entries
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: <yael.chemla@xxxxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH 2/2] multipathd: fix reservation_key check
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/2] multipathd: add failures path format wildcard
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH] multipath-tools: remove "c" from __cpluscplus, misspelled
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [LSF/MM TOPIC] Extended copy
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
• [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm bufio: fix buffer alignment
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• [PATCH] SLUB: Do not fallback to mininum order if __GFP_NORETRY is set
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: multipathd will not set the iscsi session tmo after iscsi sesstion recovery
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH] dm-integrity: use kvfree
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: multipathd will not set the iscsi session tmo after iscsi sesstion recovery
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [patch 2/2] dm-delay: add third flush class
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 2/2] dm-delay: add third flush class
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH RESEND 2/2] lvm2: 69-dm-lvm-metad.rules: set systemd vars on "change"
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [PATCH RESEND 1/2] lvm2: 69-dm-lvm-metad.rules: explicit pvscan rule
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: multipathd will not set the iscsi session tmo after iscsi sesstion recovery
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH v5 20/22] multipath -u: test if path is busy
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [patch 2/2] dm-delay: add third flush class
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 1/2] dm-delay: refactor repetitive code
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 0/2] dm-delay flush patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5 19/22] multipath -u: don't grab devices already passed to system
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v5 17/22] multipath -u: cleanup logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v5 16/22] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH RESEND 2/2] lvm2: 69-dm-lvm-metad.rules: set systemd vars on "change"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH RESEND 1/2] lvm2: 69-dm-lvm-metad.rules: explicit pvscan rule
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH RESEND 0/2] LVM2: fix lvmetad udev rules for CHANGE events
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v5 20/22] multipath -u: test if path is busy
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Patch added to scsi: scsi: scsi_dh: replace too broad "TP9" string with the exact models
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 22/22] multipath.rules: find_multipaths "smart" logic
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 21/22] libmultipath: enable find_multipaths "smart"
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 20/22] multipath -u: test if path is busy
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 19/22] multipath -u: don't grab devices already passed to system
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 18/22] multipath -u: quick check if path is multipathed
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 17/22] multipath -u: cleanup logic
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 16/22] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 15/22] libmultipath: implement find_multipaths_timeout
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 14/22] multipath -u: add DM_MULTIPATH_DEVICE_PATH=2 for "maybe"
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 13/22] multipath -u: treat failed wwids as invalid
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 12/22] multipath -u: change output to environment/key format
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 11/22] multipath -u: common code path for result message
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 10/22] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 09/22] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 08/22] libmultipath: use const char* in open_file()
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 07/22] libmultipath: change find_multipaths option to multi-value
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 06/22] libmultipath: trigger path uevent only when necessary
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 05/22] libmultipath: trigger change uevent on new device creation
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 04/22] multipath -u -i: respect entries in WWIDs file
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 03/22] libmultipath: should_multipath: keep existing maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 02/22] Revert "multipathd: imply -n if find_multipaths is set"
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v5 01/22] Revert "multipath: ignore -i if find_multipaths is set"
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH v5 17/22] multipath -u: cleanup logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 19/22] multipath -u: don't grab devices already passed to system
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 18/22] multipath -u: quick check if path is multipathed
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 13/22] multipath -u: treat failed wwids as invalid
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 07/22] libmultipath: change find_multipaths option to multi-value
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 08/22] libmultipath: use const char* in open_file()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 06/22] libmultipath: trigger path uevent only when necessary
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 03/22] libmultipath: should_multipath: keep existing maps
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH ALT] multipath-tools: add licence info to README
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH ALT] multipath-tools: add licence info to README
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH v2 2/2] multipath-tools: link LICENSES/LGPL-2.0 to LICENSE.default
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 19/20] libmultipath: enable find_multipaths "smart"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 09/20] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 20/20] multipath.rules: find_multipaths "smart" logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 19/20] libmultipath: enable find_multipaths "smart"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3 17/20] multipath -u: test if path is busy
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 12/20] multipath -u: change output to environment/key format
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH] multipath-tools: add RDAC SUN/ArrayStorage to hwtable
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH v5 20/22] multipath -u: test if path is busy
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 22/22] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 21/22] libmultipath: enable find_multipaths "smart"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 15/22] libmultipath: implement find_multipaths_timeout
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 14/22] multipath -u: add DM_MULTIPATH_DEVICE_PATH=2 for "maybe"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 16/22] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 12/22] multipath -u: change output to environment/key format
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 09/22] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 11/22] multipath -u: common code path for result message
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 10/22] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 05/22] libmultipath: trigger change uevent on new device creation
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 04/22] multipath -u -i: respect entries in WWIDs file
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 02/22] Revert "multipathd: imply -n if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 00/22] multipath path classification
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v5 01/22] Revert "multipath: ignore -i if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 07/20] libmultipath: change find_multipaths option to multi-value
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 18/20] multipath -u: quick check if path is multipathed
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v3 17/20] multipath -u: test if path is busy
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] libmultipath: Fix logic in should_multipath
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH] libmultipath: Fix logic in should_multipath
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH ALT] multipath-tools: add licence info to README
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v4 18/20] multipath -u: quick check if path is multipathed
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 20/20] multipath.rules: find_multipaths "smart" logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 19/20] libmultipath: enable find_multipaths "smart"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3 17/20] multipath -u: test if path is busy
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• multipathd will not set the iscsi session tmo after iscsi sesstion recovery
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 18/20] multipath -u: quick check if path is multipathed
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v3 17/20] multipath -u: test if path is busy
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 16/20] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 16/20] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v4 09/20] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] 11-dm-mpath.rules: dont't run "multipath -U" during coldplug
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 0/4] multipathd: decrease log verbosity
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 18/20] multipath -u: quick check if path is multipathed
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 16/20] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 15/20] libmultipath: implement find_multipaths_timeout
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 13/20] multipath -u: treat failed wwids as invalid
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 11/20] multipath -u: common code path for result message
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 09/20] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v4 07/20] libmultipath: change find_multipaths option to multi-value
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH] multipath-tools: remove emacs autoconfig of kpartx/gpt.h
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 2/2] multipath-tools: link LICENSES/LGPL-2.0 to LICENSE.default
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH v2 1/2] multipath-tools: create LICENSES dir with the text of all used licences
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH] dm/raid1: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH RFC] multipath-tools: create LICENSES dir with the text of all used licences
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH RFC] multipath-tools: create LICENSES dir with the text of all used licences
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• multipath-tools 0.7.6 fossology license assessment
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH RFC] multipath-tools: create LICENSES dir with the text of all used licences
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• dm: kernel oops by divide error on v4.16+
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH] scsi: scsi_dh: replace too broad "TP9" string with the exact models
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [PATCH] 11-dm-mpath.rules: dont't run "multipath -U" during coldplug
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [git pull] device mapper changes for 4.17
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: V4.16+ kernel warning when running xfs/006
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• V4.16+ kernel warning when running xfs/006
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH 1/4] multipathd: decrease log level of "spurious uevent" message
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 4/4] libmpathpersist: decrease log level of various messages
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 3/4] multipathd: decrease log level of waiter thread start/stop msgs
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 0/4] multipathd: decrease log verbosity
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/4] libmultipath: decrease log level of uevent filter/merge messages
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 16/20] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 18/20] multipath -u: quick check if path is multipathed
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 06/20] libmultipath: trigger path uevent only when necessary
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 07/20] libmultipath: change find_multipaths option to multi-value
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 03/20] libmultipath: should_multipath: keep existing maps
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 04/20] multipath -u -i: respect entries in WWIDs file
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 02/20] Revert "multipathd: imply -n if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 20/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 19/20] libmultipath: enable find_multipaths "smart"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 14/20] multipath -u: add DM_MULTIPATH_DEVICE_PATH=2 for "maybe"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 13/20] multipath -u: treat failed wwids as invalid
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 15/20] libmultipath: implement find_multipaths_timeout
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 12/20] multipath -u: change output to environment/key format
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 11/20] multipath -u: common code path for result message
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 08/20] libmultipath: use const char* in open_file()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 09/20] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 00/20] multipath path classification
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 05/20] libmultipath: trigger change uevent on new device creation
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v4 01/20] Revert "multipath: ignore -i if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 5/6] mpathcmd: fix libmpathcmd license
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 4/6] multipathd: remove unneeded function parameter
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 3/6] multipathd: minor dmevents polling code cleanups
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 2/6] multipath: add comments
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/6] multipathd: remove incorrect pthread_testcancel
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: device mapper ioctl handling
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: device mapper ioctl handling
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: fix DAX dependency
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: device mapper ioctl handling
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix DAX dependency
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• device mapper ioctl handling
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: fix DAX dependency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [dm:for-next 31/31] drivers/md/dm-zoned-target.c:954:20: error: initialization from incompatible pointer type
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH v9] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v9] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: Recent kernels fail to boot on POWER8 with multipath SCSI
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: Recent kernels fail to boot on POWER8 with multipath SCSI
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• [PATCH v3 20/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 14/20] multipath -u: add DM_MULTIPATH_DEVICE_PATH=2 for "maybe"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 11/20] multipath -u: common code path for result message
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 07/20] libmultipath: change find_multipaths option to multi-value
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 05/20] libmultipath: trigger change uevent on new device creation
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 02/20] Revert "multipathd: imply -n if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 15/20] libmultipath: implement find_multipaths_timeout
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 01/20] Revert "multipath: ignore -i if find_multipaths is set"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 13/20] multipath -u: treat failed wwids as invalid
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 09/20] libmultipath: functions to indicate mapping failure in /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 03/20] libmultipath: should_multipath: keep existing maps
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 19/20] libmultipath: enable find_multipaths "smart"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 17/20] multipath -u: test if path is busy
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 18/20] multipath -u: quick check if path is multipathed
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 16/20] multipath -u : set FIND_MULTIPATHS_WAIT_UNTIL from /dev/shm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 12/20] multipath -u: change output to environment/key format
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 06/20] libmultipath: trigger path uevent only when necessary
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 08/20] libmultipath: use const char* in open_file()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 04/20] multipath -u -i: respect entries in WWIDs file
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3 00/20] multipath path classification
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [dm-thin] releasing a block and reusing it occurs in the same transaction cause metadata corruption
  • From: monty <monty_pavel@xxxxxxxx>
• Re: Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks"
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: Recent kernels fail to boot on POWER8 with multipath SCSI
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.16 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 6/6] libmultipath: don't print undefined values
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 5/6] mpathcmd: fix libmpathcmd license
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 4/6] multipathd: remove unneeded function parameter
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/6] multipathd: minor dmevents polling code cleanups
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/6] multipathd: remove incorrect pthread_testcancel
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/6] multipath: add comments
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/6] multipath cleanup patches
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [git pull] device mapper fix for 4.16 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Recent kernels fail to boot on POWER8 with multipath SCSI
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Soft lockups using dm_snapshot
  • From: E V <eliventer@xxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH -next] dm verity: make some functions static
  • From: Wei Yongjun <weiyongjun1@xxxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2] multipath-tools: Remove trailing/leading whitespaces and reformat code
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 2/2] multipath-tools: add GPLv2 as COPYING
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 2/2] libmultipath/propsel: (re)use static const vars for origin
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 1/2] libmultipath: don't reject maps with undefined prio
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v3] dm raid: fix parse_raid_params() variable range issue
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH -next] dm verity: make some functions static
  • From: <yael.chemla@xxxxxxxxxxxx>
• [PATCH] dm rq: remove BUG_ON(!irqs_disabled) check
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: <yael.chemla@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: <yael.chemla@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: <yael.chemla@xxxxxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: <yael.chemla@xxxxxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 2/2] multipath-tools: add GPLv2 as COPYING
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/2] libmultipath/propsel: (re)use static const vars for origin
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 0/2] multipath-tools: hwhandler autodetection
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 0/4] multipath-tools: important fixes for 0.7.5
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 0/4] multipath-tools: important fixes for 0.7.5
  • From: Michael Laß <bevan@xxxxxxxxx>
• Re: Can we drop 'hardware_handler "1 alua"'?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/2] multipath-tools: add GPLv2 as COPYING
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: Can we drop 'hardware_handler "1 alua"'?
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: Can we drop 'hardware_handler "1 alua"'?
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: Can we drop 'hardware_handler "1 alua"'?
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Can we drop 'hardware_handler "1 alua"'?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 0/8] dm-bufio patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm raid: fix parse_raid_params() variable range issue
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm:dm-4.17 25/25] drivers//md/dm-verity-target.c:560:22: error: assignment from incompatible pointer type
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [dm:dm-4.17 25/25] drivers//md/dm-verity-target.c:560:22: error: assignment from incompatible pointer type
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH v2 16/20] libmultipath: enable find_multipaths "smart"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 15/20] libmultipath: implement find_multipaths_timeout
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 14/20] multipath -u: add DM_MULTIPATH_DEVICE_PATH=2 for "maybe"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 13/20] multipath -u: change output to environment/key format
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [patch 0/8] dm-bufio patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 11/20] libmultipath: don't try to set up failed wwids again
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 13/20] multipath -u: change output to environment/key format
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 12/20] multipath -u: common code path for result message
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [patch 0/8] dm-bufio patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 11/20] libmultipath: don't try to set up failed wwids again
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [patch 7/8] dm-bufio: support non-power-of-two block sizes
  • From: mpatocka@xxxxxxxxxx
• [patch 5/8] dm-bufio recorder fields in dm-buffer
  • From: mpatocka@xxxxxxxxxx
• [patch 1/8] dm-bufio: move dm-bufio.h to include/linux/
  • From: mpatocka@xxxxxxxxxx
• [patch 4/8] dm-bufio: fix slab cache attributes
  • From: mpatocka@xxxxxxxxxx
• [patch 8/8] dm-bufio: dont embed bio in dm_buffer
  • From: mpatocka@xxxxxxxxxx
• [patch 6/8] dm-bufio: use slab cache for dm_buffer
  • From: mpatocka@xxxxxxxxxx
• [patch 2/8] dm-bufio: get rid of slab cache name allocations
  • From: mpatocka@xxxxxxxxxx
• [patch 0/8] dm-bufio patches
  • From: mpatocka@xxxxxxxxxx
• [patch 3/8] dm-bufio: remove code that merges slab caches
  • From: mpatocka@xxxxxxxxxx
• Re: [PATCH v2] dm raid: fix parse_raid_params() variable range issue
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 10/20] libmultipath: indicate wwid failure in dm_addmap_create()
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Hannes Reinecke <hare@xxxxxxx>
• [dm-thin] problem about __shadow_block function
  • From: "monty_pavel@xxxxxxxx" <monty_pavel@xxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Yael Chemla <yael.chemla@xxxxxxxxxxxx>
• [PATCH 1/2] md: dm-verity: aggregate crypto API calls
  • From: Yael Chemla <yael.chemla@xxxxxxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Denis Semakin <d.semakin@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-verity: allow parallel processing of bio blocks
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] md: dm-verity: aggregate crypto API calls
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] multipath: fix rcu thread cancellation hang
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] multipathd: register threads that use rcu calls
  • From: Martin Wilck <mwilck@xxxxxxxx>
• multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 08/20] libmultipath: use const char* in open_file()
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 07/20] libmultipath: change find_multipaths option to multi-value
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/2] multipath: fix rcu thread cancellation hang
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/2] multipathd: register threads that use rcu calls
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/2] Fix RCU hang
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH] multipath-tools: replace FSF address with a www pointer
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH v2 06/20] libmultipath: trigger path uevent only when necessary
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 04/20] multipath -u -i: respect entries in WWIDs file
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 03/20] libmultipath: should_multipath: keep existing maps
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 01/20] Revert "multipath: ignore -i if find_multipaths is set"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 02/20] Revert "multipathd: imply -n if find_multipaths is set"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 3/5] libmultipath: config parser: Allow '"' in strings
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 3/5] libmultipath: config parser: Allow '"' in strings
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [multipath] Should we include python API in the codebase?
  • From: Gris Ge <fge@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH v2 1/2] libmultipath: don't reject maps with undefined prio
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 1/2] libmultipath: don't reject maps with undefined prio
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2] Add an option to dm-verity to validate hashes at most once
  • From: Patrik Torstensson <totte@xxxxxxxxxx>
• Re: [PATCH v2 1/2] libmultipath: don't reject maps with undefined prio
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 2/2] multipathd: handle errors in uxlsnr as fatal
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2] dm raid: fix parse_raid_params() variable range issue
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH v2] dm raid: fix parse_raid_params() variable range issue
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] dm raid: fix parse_raid_params() variable range issue
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• [PATCH] dm table: add support for secure erase forwarding [was: Re: Adaptation secure erase forwarding for 4.1x kernels]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm/mpath: flush workqueue only in necessary
  • From: wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx>
• Re: Patch "dm: ensure bio submission follows a depth-first tree walk" has been added to the 4.15-stable tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Patch "dm: ensure bio submission follows a depth-first tree walk" has been added to the 4.15-stable tree
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Patch "dm: ensure bio submission follows a depth-first tree walk" has been added to the 4.15-stable tree
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [RFC PATCH] multipath: flush workqueue only in necessary
  • From: Changwei Ge <ge.changwei@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: [PATCH] Fix slab name "biovec-(1<<(21-12))"
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: [PATCH] block: use 32-bit blk_status_t on Alpha
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: use 32-bit blk_status_t on Alpha
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: use 32-bit blk_status_t on Alpha
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] Fix slab name "biovec-(1<<(21-12))"
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] block: use 32-bit blk_status_t on Alpha
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• [PATCH v2 1/2] libmultipath: don't reject maps with undefined prio
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 2/2] multipathd: handle errors in uxlsnr as fatal
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 2/2] multipathd: handle errors in uxlsnr as fatal
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 2/2] multipathd: handle errors in uxlsnr as fatal
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Patch added to scsi: scsi: devinfo: remove DF arrays from HP
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Patch added to scsi: scsi: devinfo: remove dasd devices from the scsi subsystem
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] libmultipath: fallback to const prio if getprio() fails
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• Re: Add an option to dm-verity to validate hashes at most once
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Christopher Lameter <cl@xxxxxxxxx>
• [PATCH] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] libmultipath: fallback to const prio if getprio() fails
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/2] multipathd: handle errors in uxlsnr as fatal
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Revert "dm btree: use GFP_NOFS in dm_btree_del()"
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH RFC] scsi: devinfo: remove dasd devices from the scsi subsystem
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] scsi: devinfo: remove DF arrays from HP
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: [PATCH RESEND] multipathd: check and cleanup zombie paths
  • From: Chongyun Wu <wu.chongyun@xxxxxxx>
• Re: Questions around multipath failover and no_path_retry
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH RESEND] multipathd: check and cleanup zombie paths
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: [PATCH] multipathd: check and cleanup zombie paths
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] multipath-tools: replace FSF address with a www pointer
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 2/2] libmultipath: Fix recently introduced inconsistencies
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] dm raid: fix parse_raid_params() variable range issue
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] libmultipath: Fix recently introduced inconsistencies
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] Allow the compiler to verify consistency of declarations and definitions
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/3] multipathd: fix waiter thread cancelling
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 4.9 196/241] scsi: dh: add new rdac devices
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 4.4 099/134] scsi: dh: add new rdac devices
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] dm raid: use __within_range() more in parse_raid_params()
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [PATCH 2/2] libmultipath: Fix recently introduced inconsistencies
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• [PATCH 0/2] Fix recently introduced inconsistencies
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: [PATCH 1/3] multipathd: fix waiter thread cancelling
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/2] Allow the compiler to verify consistency of declarations and definitions
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• [PATCH v2 19/20] libmultipath: decrease log level of uevent filter/merge messages
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 20/20] multipathd: decrease log level of waiter thread start/stop msgs
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 15/20] libmultipath: implement find_multipaths_timeout
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 17/20] multipath.rules: find_multipaths "smart" logic
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 18/20] multipathd: decrease log level of "spurious uevent" message
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 16/20] libmultipath: enable find_multipaths "smart"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH v2 12/20] multipath -u: common code path for result message
  • From: Martin Wilck <mwilck@xxxxxxxx>