Linux Device-Mapper Development

• Thread Index

• [PATCH 24/28] multipath: implement "multipath -T"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 21/28] tests/hwtable: add test for local configuration dump
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 15/28] libmultipath: merge hwentries inside a conf file
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 22/28] libmultipath: allow printing local maps in snprint_config
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 19/28] tests/hwtable: implement configuration dump + reload test
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 14/28] libmultipath: don't merge hwentries by regex
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 20/28] libmultipath: allow dumping only "local" hwtable in snprint_config
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 09/28] tests/test-lib: cmocka helpers to simulate path and map discovery
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 10/28] tests/hwtable: tests for config file handling and hwentry merging
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 06/28] libmultipath: change prototypes of hwe_regmatch() and find_hwe()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 13/28] libmultipath: allow more than one hwentry
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 12/28] libmultipath: use vector for for pp->hwe and mp->hwe
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 07/28] libmultipath/prio: constify simple getters
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 08/28] tests/Makefile: autogenerate list of symbols to be wrapped
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 05/28] libmultipath: some const usage in hwentry handling
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 11/28] libmultipath: add debug messages to hwentry lookup/merging code
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 04/28] libmultipath/structs.c: constify some functions
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 01/28] kpartx: no need to use FREE_CONST
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 03/28] libmultipath: remove superfluous conditionals in load_config()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 00/28] multipath-tools: improve config file handling
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 02/28] libmultipath: fix memory leak in process_config_dir()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH] multipath.conf.5: update the description of marginal_path_err_rate_threshold
  • From: Wang Ke <wangke16@xxxxxxxxxx>
• [PATCH v2] dm-writecache: use low watermark
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: next-20180605 - kernel tried to execute NX-protected page - exploit attempt?
  • From: valdis.kletnieks@xxxxxx
• Re: next-20180605 - kernel tried to execute NX-protected page - exploit attempt?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• next-20180605 - kernel tried to execute NX-protected page - exploit attempt?
  • From: valdis.kletnieks@xxxxxx
• [PATCH] dm-writecache: use low watermark
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: writecache: fix autocommit_time option
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] mpathpersist: add all_tg_pt option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: Add block level changes for inline encryption
  • From: Ladvine D Almeida <Ladvine.DAlmeida@xxxxxxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH] dm: writecache: fix autocommit_time option
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 1/2] mpathpersist: add all_tg_pt option
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/2] multipath: don't check timestamps without a path
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/2] mpathpersist: add all_tg_pt option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 1/2] mpathpersist: fix aptpl support
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] mpathpersist: add all_tg_pt option
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 9/9] dm-integrity: recalculate checksums
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/9] dm-integrity: flush journal on suspend when using separate device
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/9] dm-integrity: add ic->start in get_data_sector
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/9] dm-integrity: allow external devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/9] dm-integrity: change the variable suspending from bool to int
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/9] dm-integrity: report size in the status
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/9] dm-integrity: use version 2 for separate metadata
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/9] dm-integrity: dont join the paths in dm_integrity_map_continue
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/9] dm-integrity: implement fair range locks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/9] dm-integrity patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 1/3] dm-writecache: convert swait_queues to wait_queues
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 2/3] dm-writecache: convert wait queue to wake_up_process
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 3/3] dm-writecache: rework writecache_flush_thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch 0/3] [PATCH 0/3] dm-writecache patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Ladvine D Almeida <Ladvine.DAlmeida@xxxxxxxxxxxx>
• Re: [PATCH 2/2] multipath: don't check timestamps without a path
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [Bug] kernel oops when running xfstests(ext4) generic/081
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 1/2] mpathpersist: fix aptpl support
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/2] multipath: don't check timestamps without a path
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/2] More miscellaneous patches
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: KASAN vs ZONE_DEVICE (was: Re: [PATCH v2 2/7] dax: change bdev_dax_supported()...)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: KASAN vs ZONE_DEVICE (was: Re: [PATCH v2 2/7] dax: change bdev_dax_supported()...)
  • From: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [Bug] kernel oops when running xfstests(ext4) generic/081
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH v2 4/7] dm: prevent DAX mounts if not supported
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Ladvine D Almeida <Ladvine.DAlmeida@xxxxxxxxxxxx>
• Re: dm-crypt: fix warning in shutdown path
  • From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
• [Bug] kernel oops when running xfstests(ext4) generic/081
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• KASAN vs ZONE_DEVICE (was: Re: [PATCH v2 2/7] dax: change bdev_dax_supported()...)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: "Kani, Toshi" <toshi.kani@xxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] branch-check: fix long->int truncation when profiling branches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] branch-check: fix long->int truncation when profiling branches
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (md/dm-writecache.c)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [git pull] device mapper changes for 4.18
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (md/dm-writecache.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (md/dm-writecache.c)
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (md/dm-writecache.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [git pull] device mapper changes for 4.18
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH] dm-crypt: fix warning in shutdown path
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• Re: [bisect BUG] dm-crypt percpu counter warnings and invalid kernel paging request at virtual address
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH v2 3/7] dm: fix test for DAX device support
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [bisect BUG] dm-crypt percpu counter warnings and invalid kernel paging request at virtual address
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [bisect BUG] dm-crypt percpu counter warnings and invalid kernel paging request at virtual address
  • From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-crypt: fix warning in shutdown path
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm-crypt: fix warning in shutdown path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-crypt: fix warning in shutdown path
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/2] libmultipath: remove rbd code
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• Re: [bisect BUG] dm-crypt percpu counter warnings and invalid kernel paging request at virtual address
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 2/2] libmultipath: remove rbd code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/2] mpathpersist: add all_tg_pt option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 4/7] dm: prevent DAX mounts if not supported
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 3/7] dm: fix test for DAX device support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 3/7] dm: fix test for DAX device support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 3/7] dm: fix test for DAX device support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH -next] dm writecache: fix return value check in writecache_ctr()
  • From: Wei Yongjun <weiyongjun1@xxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH -next] dm writecache: fix return value check in writecache_ctr()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH -next] dm writecache: fix return value check in writecache_ctr()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@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: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Ladvine D Almeida <Ladvine.DAlmeida@xxxxxxxxxxxx>
• 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: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] dm-writecache changes
  • From: Mikulas Patocka <mpatocka@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: Mikulas Patocka <mpatocka@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: Mikulas Patocka <mpatocka@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: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• 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: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-writecache patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/4] x86: optimize memcpy_flushcache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/4] dm-writecache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/4] dm-writecache patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/4] branch-check: fix long->int truncation when profiling branches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/4] swait: export the symbols __prepare_to_swait and __finish_swait
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [bug report] dm: add writecache target
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] dm-writecache: fix compilation issue with !DAX
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] branch-check: fix long->int truncation when profiling branches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: writecache: fix format string warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 4/7] dm: prevent DAX mounts if not supported
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 1/7] fs: allow per-device dax status checking for filesystems
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 7/7] dm-error: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 0/7] Fix DM DAX handling
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 6/7] dm-snap: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH] dm-writecache: fix compilation issue with !DAX
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH v2 3/7] dm: fix test for DAX device support
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] Provide more fine grained control over multipathing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: dm: writecache: fix format string warning
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH][next] dm writecache: fix missing goto in error handling code
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: writecache: add DAX dependency
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns
  • From: Vito Caputo <vcaputo@xxxxxxxxxxx>
• [PATCH] Update in the description of marginal_path_err_rate_threshold
  • From: Muneendra <muneendra.kumar@xxxxxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• 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: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns
  • From: Enric Balletbo Serra <eballetbo@xxxxxxxxx>
• Re: [PATCH] md: dm-crypt: Add Inline Encryption support for dmcrypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] dm: writecache: fix format string warning
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH] dm: writecache: add DAX dependency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] multipath.conf.5: clarify property whitelist handling
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] libmultipath: print correct default for delay_*_checks
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH resend 6/7] dm-snap: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH][next] dm writecache: fix missing goto in error handling code
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• [PATCH resend 1/7] fs: allow per-device dax status checking for filesystems
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 7/7] dm-error: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 0/7] Fix DM DAX handling
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 3/7] dm: fix test for DAX device support
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/7] fs: allow per-device dax status checking for filesystems
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH resend 4/7] dm: prevent DAX mounts if not supported
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH 4/7] dm: prevent DAX mounts if not supported
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 1/7] fs: allow per-device dax status checking for filesystems
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH resend 1/7] fs: allow per-device dax status checking for filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 4/7] dm: prevent DAX mounts if not supported
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] fs: allow per-device dax status checking for filesystems
  • From: "Darrick J. Wong" <darrick.wong@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>
• [PATCH 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 4/7] dm: prevent DAX mounts if not supported
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 0/7] Fix DM DAX handling
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 7/7] dm-error: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 6/7] dm-snap: remove unnecessary direct_access() stub
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 1/7] fs: allow per-device dax status checking for filesystems
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 3/7] dm: fix test for DAX device support
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/7] fs: allow per-device dax status checking for filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 2/7] dax: change bdev_dax_supported() to support boolean returns
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [patch 4/4] dm-writecache: use new API for flushing
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2] x86: optimize memcpy_flushcache
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• 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>