Linux Device-Mapper Development

• Thread Index

• Re: [PATCH 4/6] libmpathpersist: fix byte swapping for big endian systems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 4/6] libmpathpersist: fix byte swapping for big endian systems
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: [PATCH 1/6] libmpathpersist: remove duplicate test in readfullstatus
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 6/6] libmultipath: fix gcc 8.1 "truncated output" warnings
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 3/6] libmpathpersist: fix stack overflow in mpath_format_readfullstatus()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 5/6] (lib)mpathpersist: use O_RDONLY file descriptors
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/6] libmpathpersist: remove duplicate test in readfullstatus
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 4/6] libmpathpersist: fix byte swapping for big endian systems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/6] libmpathpersist: fix typo in mpath_format_readfullstatus
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [dm:for-next 6/8] drivers/md/dm-writecache.c:862:24: error: implicit declaration of function 'array_size'; did you mean '__ua_size'?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [dm:for-next 6/8] drivers/md/dm-writecache.c:862:24: error: implicit declaration of function 'array_size'; did you mean '__ua_size'?
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH v2] dm-zoned: Avoid triggering reclaim from inside dmz_map()
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• [PATCH] dm-zoned: Avoid triggering reclaim from inside dmz_map()
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH] dm raid: don't use 'const' in function return
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH 4.17.0-rc3 1/2] dm: Reduce line length
  • From: Ssemagoye Umar Munddu <ssemagoyeumar@xxxxxxxxx>
• Re: [PATCH v2 RESEND] x86: optimize memcpy_flushcache
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v2 RESEND] x86: optimize memcpy_flushcache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm cache: require io_mode cache feature selection to be mutually exclusive
  • From: John Pittman <jpittman@xxxxxxxxxx>
• Re: [PATCH 04/11] dm verity fec: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v2 RESEND] x86: optimize memcpy_flushcache
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH 4.17.0-rc3 1/2] dm: Reduce line length
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] multipath-tools: fix help for hds prio
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] multipath-tools: fix help for hds prio
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH 11/11] crypto: skcipher: Remove VLA usage for SKCIPHER_REQUEST_ON_STACK
  • From: Christophe Leroy <christophe.leroy@xxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH 06/11] crypto: cbc: Remove VLA usage
  • From: Christophe Leroy <christophe.leroy@xxxxxx>
• Re: [PATCH 03/11] crypto: ahash: Remove VLA usage
  • From: Christophe Leroy <christophe.leroy@xxxxxx>
• Re: [PATCH 01/11] crypto: shash: Remove VLA usage
  • From: Christophe LEROY <christophe.leroy@xxxxxx>
• Re: [PATCH 01/11] crypto: shash: Remove VLA usage
  • From: Christophe Leroy <christophe.leroy@xxxxxx>
• Re: [PATCH 04/11] dm verity fec: Remove VLA usage
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: monty <monty_pavel@xxxxxxxx>
• Re: [PATCH 07/11] crypto: xcbc: Remove VLA usage
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 05/11] crypto alg: Introduce max blocksize and alignmask
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 09/11] crypto: shash: Remove VLA usage in unaligned hashing
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 07/11] crypto: xcbc: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 05/11] crypto alg: Introduce max blocksize and alignmask
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 09/11] crypto: shash: Remove VLA usage in unaligned hashing
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 07/11] crypto: xcbc: Remove VLA usage
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 04/11] dm verity fec: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 06/11] crypto: cbc: Remove VLA usage
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 05/11] crypto alg: Introduce max blocksize and alignmask
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 04/11] dm verity fec: Remove VLA usage
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 01/11] crypto: shash: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 11/11] crypto: skcipher: Remove VLA usage for SKCIPHER_REQUEST_ON_STACK
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 01/11] crypto: shash: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 11/11] crypto: skcipher: Remove VLA usage for SKCIPHER_REQUEST_ON_STACK
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH 11/11] crypto: skcipher: Remove VLA usage for SKCIPHER_REQUEST_ON_STACK
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 08/11] crypto: qat: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 09/11] crypto: shash: Remove VLA usage in unaligned hashing
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 01/11] crypto: shash: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 06/11] crypto: cbc: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 05/11] crypto alg: Introduce max blocksize and alignmask
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 02/11] dm integrity: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 04/11] dm verity fec: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 10/11] crypto: ahash: Remove VLA usage for AHASH_REQUEST_ON_STACK
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 03/11] crypto: ahash: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 00/11] crypto: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH 07/11] crypto: xcbc: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v2 4/7] dm: prevent DAX mounts if not supported
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [RFC] kill bio_clone_kmalloc and bio_clone_bioset
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: monty <monty_pavel@xxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm thin: superblock may write succeed before other metadata blocks because of wirting metadata in async mode.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 3/6] exofs: use bio_clone_fast in _write_mirror
  • From: Boaz Harrosh <ooo@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/6] bcache: don't clone bio in bch_data_verify
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 5/5] Input: evdev - Switch to bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 2/5] bitmap: Drop unnecessary 0 check for u32 array operations
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH 3/6] exofs: use bio_clone_fast in _write_mirror
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 6/6] block: unexport bio_clone_bioset
  • From: Christoph Hellwig <hch@xxxxxx>
• [RFC] kill bio_clone_kmalloc and bio_clone_bioset
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/6] dm: use bio_split() when splitting out the already processed bio
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 5/6] md: remove a bogus comment
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/6] bcache: don't clone bio in bch_data_verify
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/6] block: remove bio_clone_kmalloc
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: writecache: Use 2-factor allocator arguments
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 00/28] multipath-tools: improve config file handling
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] dm: writecache: Use 2-factor allocator arguments
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] dm: writecache: Use 2-factor allocator arguments
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] x86: optimize memcpy_flushcache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 RESEND] x86: optimize memcpy_flushcache
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: x86: optimize memcpy_flushcache
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] x86: optimize memcpy_flushcache
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 30/30] fixup "libmultipath: merge hwentries inside a conf file"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 29/30] tests/hwtable: add test for broken hwentry filtering
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• How to reattach a disconnected device with active device-mapper mappings on top
  • From: Fedja Beader <fedja@xxxxxxxxxxxxx>
• [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• [PATCH v2 2/5] bitmap: Drop unnecessary 0 check for u32 array operations
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH 15/28] libmultipath: merge hwentries inside a conf file
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 9/9] dm-integrity: recalculate checksums
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 15/28] libmultipath: merge hwentries inside a conf file
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH] multipath-tools: remove unused SCSI_REV_SIZE
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH] multipath-tools: remove unused SCSI_REV_SIZE
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• [PATCH] Fix lintian complaint about bad whatis entry
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: why does __split_and_process_bio use bio_clone_bioset?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [bug report] dm verity: add support for forward error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [bug report] dm verity: add support for forward error correction
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• why does __split_and_process_bio use bio_clone_bioset?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: jing xia <jing.xia.mail@xxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: jing xia <jing.xia.mail@xxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Michal Hocko <mhocko@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: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH RESEND] slab: introduce the flag SLAB_MINIMIZE_WASTE
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [Query] Failed to create dm-crypt device when using AEAD type
  • From: Xiongfeng Wang <wangxiongfeng2@xxxxxxxxxx>
• [PATCH] dm bufio: Reduce dm_bufio_lock contention
  • From: Jing Xia <jing.xia.mail@xxxxxxxxx>
• Re: dm bufio: Reduce dm_bufio_lock contention
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [Query] Failed to create dm-crypt device when using AEAD type
  • From: Xiongfeng Wang <wangxiongfeng2@xxxxxxxxxx>
• Re: [Query] Failed to create dm-crypt device when using AEAD type
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [git pull v2] device mapper changes for 4.18
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH] multipath.conf.5: update the description of marginal_path_err_rate_threshold
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: next-20180605 - kernel tried to execute NX-protected page - exploit attempt?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: next-20180605 - kernel tried to execute NX-protected page - exploit attempt?
  • From: valdis.kletnieks@xxxxxx
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch 2/3 v2] dm-writecache: convert wait queue to wake_up_process
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 26/28] libmultipath: implement and use blacklist merging
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 28/28] multipath.conf(5): various corrections and clarifications
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 25/28] libmultipath: merge "multipath" config sections by wwid
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 18/28] multipath, multipathd: consolidate config dumping
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 27/28] libmultipath: escape '"' chars while dumping config
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 16/28] libmultipath/hwtable: remove inherited props from ONTAP NVMe
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 23/28] multipathd: implement "show config local"
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 17/28] libmultipath: don't merge by regex in setup_default_blist()
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [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>