Linux Device-Mapper Development

• Date Index

• Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, (continued)
  • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mike Snitzer
  • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Pavel Machek
    • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mike Galbraith
    • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Kent Overstreet
      • Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset, kbuild test robot
      • Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset, kbuild test robot
      • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mike Galbraith
      • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mike Snitzer
        • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Kent Overstreet
          • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mikulas Patocka
          • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Mike Snitzer
  • Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone, Ming Lei
• [PATCH v5 0/3] init: add support to directly boot to a mapped device, Kees Cook
  • [PATCH v5 2/3] dm: make mapped_device locking functions available, Kees Cook
  • [PATCH v5 3/3] init: add support to directly boot to a mapped device, Kees Cook
  • [PATCH v5 1/3] dm: export a table+mapped device to the ioctl interface, Kees Cook
  • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Alasdair G Kergon
    • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Kees Cook
      • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Mike Snitzer
        • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Kees Cook
          • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Mike Snitzer
            • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Kees Cook
              • Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device, Mike Snitzer
• [PATCH]multipath-tools: select reservation_key parameter before PR handler for first path addition to new map, Shiva Krishna
• dm-lazymirror advice, Mailing Lists
• Occasional dmsetup resume lockups, Richard Davies
  • Re: Occasional dmsetup resume lockups, Zdenek Kabelac
    • Re: Occasional dmsetup resume lockups, Richard Davies
• [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure, Germano Percossi
  • Re: [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure, Germano Percossi
  • Re: [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure, Germano Percossi
    • Re: [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure, Christophe Varoqui
• [PATCH] [dm-cache] Make the mq policy an alias for smq, Joe Thornber
  • Re: [PATCH] [dm-cache] Make the mq policy an alias for smq, John Stoffel
    • Re: [PATCH] [dm-cache] Make the mq policy an alias for smq, Joe Thornber
      • Re: [PATCH] [dm-cache] Make the mq policy an alias for smq, John Stoffel
  • Re: Make the mq policy an alias for smq, Mike Snitzer
    • Re: Make the mq policy an alias for smq, Joe Thornber
    • Re: Make the mq policy an alias for smq, Joe Thornber
      • Re: Make the mq policy an alias for smq, Mike Snitzer
        • Re: Make the mq policy an alias for smq, Joe Thornber
  • Re: [PATCH] [dm-cache] Make the mq policy an alias for smq, Joe Thornber
• [patch] dm: check for kmalloc failure in dm_init_request_based_blk_mq_queue(), Dan Carpenter
  • Re: [patch] dm: check for kmalloc failure in dm_init_request_based_blk_mq_queue(), Johannes Thumshirn
  • Re: dm: check for kmalloc failure in dm_init_request_based_blk_mq_queue(), Mike Snitzer
• [PATCH v2 00/15] dm: improve request-based DM and multipath, Mike Snitzer
  • [dm-4.6 PATCH v2 13/15] dm mpath: use blk_mq_alloc_request() and blk_mq_free_request() directly, Mike Snitzer
  • [dm-4.6 PATCH v2 08/15] dm: allocate blk_mq_tag_set rather than embed in mapped_device, Mike Snitzer
  • [dm-4.6 PATCH v2 14/15] dm mpath: reduce granularity of locking in __multipath_map, Mike Snitzer
  • [dm-4.6 PATCH v2 03/15] dm: cleanup dm_any_congested(), Mike Snitzer
  • [dm-4.6 PATCH v2 12/15] dm mpath: cleanup 'struct dm_mpath_io' management code, Mike Snitzer
  • [dm-4.6 PATCH v2 07/15] dm: add 'blk_mq_nr_hw_queues' and 'blk_mq_queue_depth' module params, Mike Snitzer
  • [dm-4.6 PATCH v2 04/15] dm: set DM_TARGET_WILDCARD feature on "error" target, Mike Snitzer
  • [dm-4.5 PATCH v2 01/15] dm: fix excessive dm-mq context switching, Mike Snitzer
  • [dm-4.6 PATCH v2 02/15] dm: remove unused dm_get_rq_mapinfo(), Mike Snitzer
  • [dm-4.6 PATCH v2 05/15] dm: optimize dm_mq_queue_rq(), Mike Snitzer
  • [dm-4.6 PATCH v2 11/15] dm mpath: use blk-mq pdu for per-request 'struct dm_mpath_io', Mike Snitzer
  • [dm-4.6 PATCH v2 06/15] dm: optimize dm_request_fn(), Mike Snitzer
  • [dm-4.6 PATCH v2 09/15] dm: rename target's per_bio_data_size to per_io_data_size, Mike Snitzer
  • [dm-4.6 PATCH v2 10/15] dm: allow immutable request-based targets to use blk-mq pdu, Mike Snitzer
  • [dm-4.6 PATCH v2 15/15] dm mpath: remove unnecessary casts in front of ti->private, Mike Snitzer
• [PATCH] dm-mpath: fix a tiny case which can cause an infinite loop, jiangyiwen
  • Re: dm-mpath: fix a tiny case which can cause an infinite loop, Mike Snitzer
    • Re: dm-mpath: fix a tiny case which can cause an infinite loop, jiangyiwen
      • Re: dm-mpath: fix a tiny case which can cause an infinite loop, Mike Snitzer
        • Re: dm-mpath: fix a tiny case which can cause an infinite loop, Martin K. Petersen
        • Re: dm-mpath: fix a tiny case which can cause an infinite loop, jiangyiwen
• [PATCH] block: do not return -EOPNOTSUPP only when issue a discard request, jiangyiwen
  • Re: [PATCH] block: do not return -EOPNOTSUPP only when issue a discard request, Lukáš Czerner
  • Re: [PATCH] block: do not return -EOPNOTSUPP only when issue a discard request, Martin K. Petersen
• Why don't return -EOPNOTSUPP?, jiangyiwen
  • Re: Why don't return -EOPNOTSUPP?, Lukáš Czerner
    • Re: Why don't return -EOPNOTSUPP?, jiangyiwen
• Getting device-mapper failure notifications, Avishay Traeger
  • Re: Getting device-mapper failure notifications, Andy Grover
    • Re: Getting device-mapper failure notifications, Avishay Traeger
    • Re: Getting device-mapper failure notifications, Hannes Reinecke
      • Re: Getting device-mapper failure notifications, Bryn M. Reeves
      • Re: Getting device-mapper failure notifications, Mike Snitzer
• [PATCH resend] [dm]fix NULL pointer when create dm device, DingXiang
  • Re: [PATCH resend] [dm]fix NULL pointer when create dm device, Mike Snitzer
• [PATCH 1/3] add %g format specifier to 'multipathd show paths format' command, Todd Gill
  • [PATCH 3/3] add options to the show groups command, Todd Gill
  • [PATCH 2/3] add 'show groups' command to multipathd, Todd Gill
  • Re: [PATCH 1/3] add %g format specifier to 'multipathd show paths format' command, Benjamin Marzinski
  • [PATCH v2 1/3] Add %g format specifier to 'multipathd show paths format' command, Todd Gill
    • [PATCH v2 3/3] Add options to the show groups command, Todd Gill
    • [PATCH v2 2/3] Add 'show groups' command to multipathd, Todd Gill
• Re: 4.5-rc1 multipath regression, Bart Van Assche
  • Re: 4.5-rc1 multipath regression, Mike Snitzer
    • Re: 4.5-rc1 multipath regression, Bart Van Assche
      • Re: 4.5-rc1 multipath regression, Mike Snitzer
• [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Benjamin Marzinski
  • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Mike Snitzer
    • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Benjamin Marzinski
      • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Benjamin Marzinski
        • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Mike Snitzer
  • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Hannes Reinecke
    • Re: [LSF/MM ATTEND] multipath redesign and dm blk-mq issues, Benjamin Marzinski
• reinstate dm target local ioctl support, Andy Whitcroft
  • Re: reinstate dm target local ioctl support, Christoph Hellwig
  • Re: reinstate dm target local ioctl support, Joe Thornber
  • Re: reinstate dm target local ioctl support, Alasdair G Kergon
    • Re: reinstate dm target local ioctl support, Andy Whitcroft
• Re: Target and deduplication?, Christoph Hellwig
  • Re: Target and deduplication?, Joe Thornber
    • Re: Target and deduplication?, Nikolay Borisov
  • Re: Target and deduplication?, Mike Snitzer
    • Re: Target and deduplication?, Alex Gorbachev
    • Re: Target and deduplication?, Christoph Hellwig
• [PATCH] Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
  • Re: [PATCH] Introducing multipath C API <libdmmp/libdmmp.h>, Hannes Reinecke
    • Re: [PATCH] Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
    • Re: [PATCH] Introducing multipath C API <libdmmp/libdmmp.h>, Todd Gill
      • Re: [PATCH] Introducing multipath C API <libdmmp/libdmmp.h>, Hannes Reinecke
        • [PATCH V2] Introducing multipath C API., Gris Ge
          • [PATCH V2] Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
            • Re: [PATCH V2] Introducing multipath C API <libdmmp/libdmmp.h>, Benjamin Marzinski
              • Re: [PATCH V2] Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
            • [PATCH V3 0/3] Introducing multipath C API, Gris Ge
              • [PATCH V3 2/3] multipath-tools: Set errno mpath_recv_reply() when failure., Gris Ge
              • [PATCH V3 1/3] multipath-tools: Increase MAX_REPLY_LEN., Gris Ge
                • Re: [PATCH V3 1/3] multipath-tools: Increase MAX_REPLY_LEN., Hannes Reinecke
                  • Re: [PATCH V3 1/3] multipath-tools: Increase MAX_REPLY_LEN., Gris Ge
                    • Re: [PATCH V3 1/3] multipath-tools: Increase MAX_REPLY_LEN., Hannes Reinecke
                      • Re: [PATCH V3 1/3] multipath-tools: Increase MAX_REPLY_LEN., Gris Ge
                        • [PATCH V4 0/3] Introducing multipath C API, Gris Ge
                          • [PATCH V4 2/3] multipath-tools: Set errno mpath_recv_reply() when failure, Gris Ge
                          • [PATCH V4 1/3] multipath-tools: New way to limit the IPC command length., Gris Ge
                          • Re: [PATCH V4 0/3] Introducing multipath C API, Gris Ge
                          • [PATCH V5 0/3] Introducing multipath C API, Gris Ge
                            • [PATCH V5 1/3] multipath-tools: New way to limit the IPC command length., Gris Ge
                            • [PATCH V5 2/3] multipath-tools: Set errno mpath_recv_reply() when failure, Gris Ge
                            • [PATCH V5 3/3] multipath-tools: Introducing multipath C API, Gris Ge
                          • Please ignore this patch set. ([PATCH V4 0/3] Introducing multipath C API), Gris Ge
                          • [PATCH V4 3/3] multipath-tools: Introducing multipath C API, Gris Ge
              • [PATCH V3 3/3] multipath-tools: Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
              • [PATCH 3/3] multipath-tools: Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
              • [PATCH V3 3/3] multipath-tools: Introducing multipath C API <libdmmp/libdmmp.h>, Gris Ge
  • [PATCH V6 0/3] Introducing multipath C API, Gris Ge
    • [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Gris Ge
      • Re: [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Benjamin Marzinski
        • Re: [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Gris Ge
        • Re: [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Bart Van Assche
          • Re: [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Benjamin Marzinski
            • Re: [PATCH V6 1/3] multipath-tools: New way to limit the IPC command length., Bart Van Assche
    • [PATCH V6 2/3] multipath-tools: Set errno mpath_recv_reply() when failure, Gris Ge
    • [PATCH V6 3/3] multipath-tools: Introducing multipath C API, Gris Ge
    • Re: [PATCH V6 0/3] Introducing multipath C API, Benjamin Marzinski
  • [PATCH V7 0/4] multipath: Introducing multipath C API, Gris Ge
    • [PATCH V7 2/4] multipath-tools: New way to limit the IPC command length., Gris Ge
      • Re: [PATCH V7 2/4] multipath-tools: New way to limit the IPC command length., Bart Van Assche
      • Re: [PATCH V7 2/4] multipath-tools: New way to limit the IPC command length., Benjamin Marzinski
    • [PATCH V7 1/4] libmpathcmd: Block SIGPIPE when write(), Gris Ge
      • Re: [PATCH V7 1/4] libmpathcmd: Block SIGPIPE when write(), Bart Van Assche
    • [PATCH V7 3/4] multipath-tools: Set errno mpath_recv_reply() when failure, Gris Ge
    • Re: [PATCH V7 0/4] multipath: Introducing multipath C API, Gris Ge
    • [PATCH V7 4/4] multipath-tools: Introducing multipath C API, Gris Ge
      • [PATCH V5] multipath-tools: Introducing multipath C API, Gris Ge
      • [PATCH V5] multipath-tools: Introducing multipath C API, Gris Ge
        • Re: [PATCH V5] multipath-tools: Introducing multipath C API, Christophe Varoqui
• LVM thin provisioning actual status, Никифоров Руслан
  • Re: LVM thin provisioning actual status, Mike Snitzer
• Re: [PATCH 9/26] eCryptfs: Use skcipher and shash, Julia Lawall
  • [v2 PATCH 9/26] eCryptfs: Use skcipher and shash, Herbert Xu
    • Re: [v2 PATCH 9/26] eCryptfs: Use skcipher and shash, Tyler Hicks
• [PATCH 0/26] crypto: Use skcipher and ahash/shash where possible, Herbert Xu
  • [PATCH 7/26] wusb: Use skcipher, Herbert Xu
    • Re: [PATCH 7/26] wusb: Use skcipher, kbuild test robot
  • [PATCH 8/26] cifs: Use skcipher, Herbert Xu
  • [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms, Herbert Xu
    • Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms, kbuild test robot
    • Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms, David Miller
  • [PATCH 17/26] mac802154: Use skcipher, Herbert Xu
    • Re: [PATCH 17/26] mac802154: Use skcipher, Stefan Schmidt
  • [PATCH 12/26] sunrpc: Use skcipher and ahash/shash, Herbert Xu
  • [PATCH 20/26] drbd: Use shash and ahash, Herbert Xu
  • [PATCH 16/26] libceph: Use skcipher, Herbert Xu
    • Re: [PATCH 16/26] libceph: Use skcipher, Ilya Dryomov
      • Re: [PATCH 16/26] libceph: Use skcipher, Herbert Xu
        • Re: [PATCH 16/26] libceph: Use skcipher, Ilya Dryomov
          • Re: [PATCH 16/26] libceph: Use skcipher, Herbert Xu
  • [PATCH 21/26] nfc: s3fwrn5: Use shash, Herbert Xu
    • Re: [PATCH 21/26] nfc: s3fwrn5: Use shash, kbuild test robot
  • [PATCH 13/26] lib80211: Use skcipher and ahash, Herbert Xu
  • [PATCH 24/26] nfsd: Use shash, Herbert Xu
    • Re: [PATCH 24/26] nfsd: Use shash, kbuild test robot
  • [PATCH 11/26] f2fs: Use skcipher, Herbert Xu
  • [PATCH 1/26] block: cryptoloop - Use new skcipher interface, Herbert Xu
    • Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface, kbuild test robot
      • Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface, Herbert Xu
  • [PATCH 4/26] dm crypt: Use skcipher and ahash, Herbert Xu
    • Re: [PATCH 4/26] dm crypt: Use skcipher and ahash, kbuild test robot
  • [PATCH 25/26] sctp: Use shash, Herbert Xu
    • Re: [PATCH 25/26] sctp: Use shash, David Miller
  • [PATCH 9/26] eCryptfs: Use skcipher and shash, Herbert Xu
    • Re: [PATCH 9/26] eCryptfs: Use skcipher and shash, kbuild test robot
  • [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash, Herbert Xu
    • Re: [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash, Greg KH
  • [PATCH 18/26] rxrpc: Use skcipher, Herbert Xu
  • [PATCH 5/26] orinoco: Use ahash, Herbert Xu
  • [PATCH 2/26] ppp_mppe: Use skcipher and ahash, Herbert Xu
  • [PATCH 23/26] iscsi-target: Use shash and ahash, Herbert Xu
  • [PATCH 14/26] KEYS: Use skcipher, Herbert Xu
  • [PATCH 26/26] tcp: Use ahash, Herbert Xu
    • Re: [PATCH 26/26] tcp: Use ahash, David Miller
  • [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash, Herbert Xu
    • Re: [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash, Greg KH
  • [PATCH 10/26] ext4: Use skcipher, Herbert Xu
  • [PATCH 22/26] iscsi_tcp: Use ahash, Herbert Xu
    • Re: [PATCH 22/26] iscsi_tcp: Use ahash, Mike Christie
  • [PATCH 15/26] Bluetooth: Use skcipher and hash, Herbert Xu
    • Re: [PATCH 15/26] Bluetooth: Use skcipher and hash, kbuild test robot
    • Re: [PATCH 15/26] Bluetooth: Use skcipher and hash, Marcel Holtmann
• [PATCH v2] dm pref-path: provides preferred path load balance policy, Ravikanth Nalla
  • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Hannes Reinecke
    • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Mike Snitzer
      • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Nalla, Ravikanth
        • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Benjamin Marzinski
          • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Hannes Reinecke
            • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Benjamin Marzinski
              • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Benjamin Marzinski
  • Re: [PATCH v2] dm pref-path: provides preferred path load balance policy, Benjamin Marzinski
• [PATCH V2] kpartx: support device names with spaces, Mauricio Faria de Oliveira
  • Re: [PATCH V2] kpartx: support device names with spaces, Christophe Varoqui
    • Re: [PATCH V2] kpartx: support device names with spaces, Mauricio Faria de Oliveira
    • [PATCH] Fix loopback file with kpartx -av, Mathieu Trudel-Lapierre
      • Re: [PATCH] Fix loopback file with kpartx -av, Christophe Varoqui
• dm-cache + storage client experiment, mlody3k .
  • Re: dm-cache + storage client experiment, John Stoffel
  • Re: dm-cache + storage client experiment, Mike Snitzer
• I/O block when removing thin device on the same pool, Dennis Yang
  • Re: I/O block when removing thin device on the same pool, Zdenek Kabelac
    • Re: I/O block when removing thin device on the same pool, Dennis Yang
    • Re: I/O block when removing thin device on the same pool, Nikolay Borisov
      • Re: I/O block when removing thin device on the same pool, Mike Snitzer
        • Re: I/O block when removing thin device on the same pool, Lars Ellenberg
          • Re: I/O block when removing thin device on the same pool, Zdenek Kabelac
            • Re: I/O block when removing thin device on the same pool, Mike Snitzer
          • Re: I/O block when removing thin device on the same pool, Joe Thornber
            • Re: I/O block when removing thin device on the same pool, Dennis Yang
              • Re: I/O block when removing thin device on the same pool, Joe Thornber
                • Re: I/O block when removing thin device on the same pool, Dennis Yang
                  • Re: I/O block when removing thin device on the same pool, Joe Thornber
                    • Re: I/O block when removing thin device on the same pool, Dennis Yang
                      • Re: I/O block when removing thin device on the same pool, Joe Thornber
                        • Re: I/O block when removing thin device on the same pool, Dennis Yang
            • Re: I/O block when removing thin device on the same pool, Lars Ellenberg
              • Re: I/O block when removing thin device on the same pool, Joe Thornber
                • Re: I/O block when removing thin device on the same pool, Lars Ellenberg
• How can I get my sector size (via queue_limits?) from a dm_target?, Eric Wheeler
  • Re: How can I get my sector size (via queue_limits?) from a dm_target?, Mike Snitzer
• Re: dm-multipath low performance with blk-mq, Sagi Grimberg
  • Re: dm-multipath low performance with blk-mq, Mike Snitzer
    • Re: dm-multipath low performance with blk-mq, Mike Snitzer
      • Re: dm-multipath low performance with blk-mq, Benjamin Marzinski
        • Re: dm-multipath low performance with blk-mq, Mike Snitzer
          • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
            • Re: dm-multipath low performance with blk-mq, Mike Snitzer
              • Re: dm-multipath low performance with blk-mq, Christoph Hellwig
                • Re: dm-multipath low performance with blk-mq, Mike Snitzer
            • Re: dm-multipath low performance with blk-mq, Benjamin Marzinski
          • Re: dm-multipath low performance with blk-mq, Sagi Grimberg
            • Re: dm-multipath low performance with blk-mq, Mike Snitzer
              • Re: dm-multipath low performance with blk-mq, Jens Axboe
                • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                  • Re: dm-multipath low performance with blk-mq, Jens Axboe
                    • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                      • Re: dm-multipath low performance with blk-mq, Jens Axboe
              • Re: dm-multipath low performance with blk-mq, Sagi Grimberg
                • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                  • Re: dm-multipath low performance with blk-mq, Jens Axboe
                    • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                  • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
                    • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                      • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
                        • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                          • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                            • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                            • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
                              • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                                • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
                                  • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                                    • Re: dm-multipath low performance with blk-mq, Hannes Reinecke
                                      • Re: dm-multipath low performance with blk-mq, Mike Snitzer
                                • [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                  • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                    • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                      • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Sagi Grimberg
                                        • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                          • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Sagi Grimberg
                                        • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Bart Van Assche
                                          • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Sagi Grimberg
                                            • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                            • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Sagi Grimberg
                                              • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                                • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Sagi Grimberg
                                                  • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                                • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Hannes Reinecke
                                                  • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                                    • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Hannes Reinecke
                                                    • Re: [RFC PATCH] dm: fix excessive dm-mq context switching, Mike Snitzer
                                                    • RCU-ified dm-mpath for testing/review, Mike Snitzer
                                                    • Re: RCU-ified dm-mpath for testing/review, Mike Snitzer
                                                    • Re: RCU-ified dm-mpath for testing/review, Mike Snitzer
                                                    • Re: RCU-ified dm-mpath for testing/review, Hannes Reinecke
                                                    • Re: RCU-ified dm-mpath for testing/review, Mike Snitzer
                                                    • Re: RCU-ified dm-mpath for testing/review, Hannes Reinecke
                                                    • Re: RCU-ified dm-mpath for testing/review, Mike Snitzer
                                                    • Re: RCU-ified dm-mpath for testing/review, Hannes Reinecke
      • Re: dm-multipath low performance with blk-mq, Benjamin Marzinski
      • Re: dm-multipath low performance with blk-mq, Mike Snitzer
        • Re: dm-multipath low performance with blk-mq, Christoph Hellwig
          • Re: dm-multipath low performance with blk-mq, Mike Snitzer
            • Re: dm-multipath low performance with blk-mq, Sagi Grimberg
        • Re: dm-multipath low performance with blk-mq, Benjamin Marzinski
• How can need dm use limits.max_hw_sectors from the bdev?, Eric Wheeler
  • Re: How can need dm use limits.max_hw_sectors from the bdev?, Mike Snitzer
    • Re: How can dm use limits.max_hw_sectors from the bdev?, Eric Wheeler
• Add. Sense: Data synchronization mark error, Tejas Rao
• getting support for PURE FlashArray into multipath-tools, Brian Bunker
• [PATCH RESEND] md:Check if call to thaw_bdev fails in unlock_fs, Nicholas Krause
• device mapper increased latency on RAID array, Thanos Makatos
  • Re: device mapper increased latency on RAID array, Mike Snitzer
  • Re: device mapper increased latency on RAID array, Heinz Mauelshagen
    • Re: device mapper increased latency on RAID array, Thanos Makatos
      • Re: device mapper increased latency on RAID array, Thanos Makatos
• [PATCH v2] dm stripe: document that chunk size is specified in sectors (resend), Tomohiro Kusumi
• 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits", Christian Borntraeger
  • Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits", Martin K. Petersen
    • Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits", Christian Borntraeger
      • Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits", Christian Borntraeger
        • Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits", Martin K. Petersen
• [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
  • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Alasdair G Kergon
    • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
      • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Alasdair G Kergon
  • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Sagi Grimberg
    • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
    • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Mike Snitzer
      • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
        • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Mike Snitzer
      • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Sagi Grimberg
        • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Mike Snitzer
          • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Sagi Grimberg
  • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Benjamin Marzinski
    • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
      • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Bart Van Assche
        • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Hannes Reinecke
      • Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign, Benjamin Marzinski
• [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Mike Snitzer
  • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Mikulas Patocka
    • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Hannes Reinecke
      • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Alasdair G Kergon
      • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Benjamin Marzinski
        • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Mike Snitzer
  • Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?, Sagi Grimberg
• [PATCH 1/2] dm stripe: document that chunk size is specified in sectors (resend), kusumi . tomohiro
  • Re: [PATCH 1/2] dm stripe: document that chunk size is specified in sectors (resend), Mikulas Patocka
• [PATCH 2/2] dm flakey: document that default I/O error is only for write (resend), kusumi . tomohiro
• [PATCH 00/35 v3] eparate operations from flags in the bio/request structs, mchristi
  • [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, mchristi
  • [PATCH 13/35] xfs: set bi_op to REQ_OP, mchristi
  • [PATCH 12/35] gfs2: set bi_op to REQ_OP, mchristi
  • [PATCH 03/35] block, fs, mm, drivers: set bi_op to REQ_OP, mchristi
  • [PATCH 16/35] nilfs: set bi_op to REQ_OP, mchristi
  • [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio, mchristi
  • [PATCH 09/35] btrfs: update __btrfs_map_block for bi_op transition, mchristi
  • [PATCH 18/35] pm: set bi_op to REQ_OP, mchristi
  • [PATCH 11/35] f2fs: set bi_op to REQ_OP, mchristi
  • [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio, mchristi
  • [PATCH 04/35] fs: have submit_bh users pass in op and flags separately, mchristi
  • [PATCH 17/35] ocfs2: set bi_op to REQ_OP, mchristi
  • [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately, mchristi
  • [PATCH 15/35] mpage: set bi_op to REQ_OP, mchristi
  • [PATCH 06/35] direct-io: set bi_op to REQ_OP, mchristi
  • [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op, mchristi
  • [PATCH 21/35] bcache: set bi_op to REQ_OP, mchristi
  • [PATCH 26/35] block: set op to REQ_OP, mchristi
  • [PATCH 32/35] block: shrink bi_rw and bi_op, mchristi
  • [PATCH 19/35] dm: set bi_op to REQ_OP, mchristi
  • [PATCH 28/35] blktrace: get op from req->op/bio->bi_op, mchristi
  • [PATCH 25/35] target: set bi_op to REQ_OP, mchristi
  • [PATCH 31/35] block, fs: remove old REQ definitions., mchristi
  • [PATCH 23/35] md/raid: set bi_op to REQ_OP, mchristi
  • [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs, mchristi
  • [PATCH 24/35] xen: set bi_op to REQ_OP, mchristi
  • [PATCH 20/35] dm: pass dm stats data dir instead of bi_rw, mchristi
  • [PATCH 22/35] drbd: set bi_op to REQ_OP, mchristi
  • [PATCH 29/35] ide cd: do not set REQ_WRITE on requests., mchristi
  • [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation, mchristi
  • [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua, mchristi
  • [PATCH 14/35] hfsplus: set bi_op to REQ_OP, mchristi
  • [PATCH 27/35] drivers: set request op to REQ_OP, mchristi
  • [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH, mchristi
  • [PATCH 08/35] btrfs: set bi_op tp REQ_OP, mchristi
  • Re: [PATCH 00/35 v3] eparate operations from flags in the bio/request structs, Christoph Hellwig
• [git pull] device mapper changes for 4.5, Mike Snitzer
• [PATCH 2/2] dm-snapshot: merge functions commit_callback and pending_complete, Mikulas Patocka
• [PATCH 1/2] dm-snapshot: fix hung bios when copy error happens, Mikulas Patocka
• please pull in commit 0fcb04d59351f to stable@ 4.1+, Mike Snitzer
• [RFC] disk doesn't spin down with thin pool + dmeventd, Alan Jenkins
  • Re: [RFC] disk doesn't spin down with thin pool + dmeventd, Zdenek Kabelac
  • Re: [RFC] disk doesn't spin down with thin pool + dmeventd, Alan Jenkins
    • Re: [RFC] disk doesn't spin down with thin pool + dmeventd, Alan Jenkins
      • Re: [RFC] disk doesn't spin down with thin pool + dmeventd, Zdenek Kabelac
• [PATCH] kpartx: support device names with spaces, Mauricio Faria de Oliveira
  • Re: [PATCH] kpartx: support device names with spaces, Christophe Varoqui
    • Re: [PATCH] kpartx: support device names with spaces, Mauricio Faria de Oliveira
• can't boot with linux-next-20160104, Jeff Moyer
• [PATCH 00/35 v2] separate operations from flags in the bio/request structs, mchristi
  • [PATCH 18/35] pm: set bi_op to REQ_OP, mchristi
  • [PATCH 14/35] hfsplus: set bi_op to REQ_OP, mchristi
  • [PATCH 16/35] nilfs: set bi_op to REQ_OP, mchristi
  • [PATCH 15/35] mpage: set bi_op to REQ_OP, mchristi
  • [PATCH 20/35] dm: pass dm stats data dir instead of bi_rw, mchristi
  • [PATCH 12/35] gfs2: set bi_op to REQ_OP, mchristi
  • [PATCH 08/35] btrfs: set bi_op tp REQ_OP, mchristi
  • [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op, mchristi
  • [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately, mchristi
    • Re: [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately, kbuild test robot
  • [PATCH 13/35] xfs: set bi_op to REQ_OP, mchristi
    • Re: [PATCH 13/35] xfs: set bi_op to REQ_OP, Dave Chinner
  • [PATCH 03/35] block, fs, mm, drivers: set bi_op to REQ_OP, mchristi
  • [PATCH 17/35] ocfs2: set bi_op to REQ_OP, mchristi
  • [PATCH 06/35] direct-io: set bi_op to REQ_OP, mchristi
  • [PATCH 21/35] bcache: set bi_op to REQ_OP, mchristi
  • [PATCH 04/35] fs: have submit_bh users pass in op and flags separately, mchristi
  • [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio, mchristi
    • Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio, Bart Van Assche
    • Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio, Christoph Hellwig
      • Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio, Mike Christie
  • [PATCH 25/35] target: set bi_op to REQ_OP, mchristi
    • Re: [PATCH 25/35] target: set bi_op to REQ_OP, Nicholas A. Bellinger
  • [PATCH 27/35] drivers: set request op to REQ_OP, mchristi
  • [PATCH 24/35] xen: set bi_op to REQ_OP, mchristi
  • [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation, mchristi
  • [PATCH 26/35] block: set op to REQ_OP, mchristi
    • Re: [PATCH 26/35] block: set op to REQ_OP, Christoph Hellwig
  • [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua, mchristi
    • Re: [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua, kbuild test robot
    • Re: [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua, Christoph Hellwig
  • [PATCH 28/35] blktrace: get op from req->op/bio->bi_op, mchristi
  • [PATCH 32/35] block: shrink bi_rw and bi_op, mchristi
  • [PATCH 23/35] md/raid: set bi_op to REQ_OP, mchristi
  • [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, mchristi
    • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Martin K. Petersen
    • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Christoph Hellwig
      • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Mike Christie
        • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Mike Christie
          • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Christoph Hellwig
        • Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields, Christoph Hellwig
  • [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs, mchristi
  • [PATCH 09/35] btrfs: update __btrfs_map_block for bi_op transition, mchristi
  • [PATCH 11/35] f2fs: set bi_op to REQ_OP, mchristi
  • [PATCH 29/35] ide cd: do not set REQ_WRITE on requests., mchristi
  • [PATCH 19/35] dm: set bi_op to REQ_OP, mchristi
  • [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio, mchristi
  • [PATCH 22/35] drbd: set bi_op to REQ_OP, mchristi
  • [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH, mchristi
    • Re: [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH, kbuild test robot
  • [PATCH 31/35] block, fs: remove old REQ definitions., mchristi
  • Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs, Martin K. Petersen
    • Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs, Dave Chinner
  • Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs, Christoph Hellwig
    • Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs, Mike Christie
      • Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs, Mike Snitzer
• [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces, Seth Forshee
  • [PATCH RESEND v2 01/18] block_dev: Support checking inode permissions in lookup_bdev(), Seth Forshee
  • [PATCH RESEND v2 07/18] fs: Check for invalid i_uid in may_follow_link(), Seth Forshee
  • [PATCH RESEND v2 02/18] block_dev: Check permissions towards block device inode when mounting, Seth Forshee
  • [PATCH RESEND v2 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns, Seth Forshee
  • [PATCH RESEND v2 03/18] fs: Treat foreign mounts as nosuid, Seth Forshee
  • [PATCH RESEND v2 18/18] fuse: Allow user namespace mounts, Seth Forshee
    • Re: [PATCH RESEND v2 18/18] fuse: Allow user namespace mounts, Miklos Szeredi
  • [PATCH RESEND v2 05/18] userns: Replace in_userns with current_in_userns, Seth Forshee
  • [PATCH RESEND v2 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns, Seth Forshee
  • [PATCH RESEND v2 15/18] fuse: Add support for pid namespaces, Seth Forshee
    • Re: [PATCH RESEND v2 15/18] fuse: Add support for pid namespaces, Miklos Szeredi
      • Re: [PATCH RESEND v2 15/18] fuse: Add support for pid namespaces, Seth Forshee
  • [PATCH RESEND v2 13/18] fs: Allow superblock owner to access do_remount_sb(), Seth Forshee
  • [PATCH RESEND v2 08/18] cred: Reject inodes with invalid ids in set_create_file_as(), Seth Forshee
  • [PATCH RESEND v2 06/18] Smack: Handle labels consistently in untrusted mounts, Seth Forshee
  • [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
    • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
      • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Eric W. Biederman
        • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
          • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Eric W. Biederman
            • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
        • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
          • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Eric W. Biederman
            • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
              • Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Eric W. Biederman
  • [PATCH RESEND v2 04/18] selinux: Add support for unprivileged mounts from user namespaces, Seth Forshee
  • [PATCH RESEND v2 14/18] capabilities: Allow privileged user in s_user_ns to set security.* xattrs, Seth Forshee
  • [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
    • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Miklos Szeredi
      • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
        • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Miklos Szeredi
          • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
            • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Miklos Szeredi
              • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
                • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Miklos Szeredi
                  • Re: [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
  • [PATCH RESEND v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant, Seth Forshee
    • Re: [PATCH RESEND v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant, Miklos Szeredi
  • [PATCH RESEND v2 10/18] fs: Update posix_acl support to handle user namespace mounts, Seth Forshee
  • Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces, Seth Forshee
    • Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces, Eric W. Biederman
      • Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces, Seth Forshee
• dm-cache: Can I change policy without suspending the cache?, Alex Sudakar
  • Re: dm-cache: Can I change policy without suspending the cache?, Joe Thornber
    • Re: dm-cache: Can I change policy without suspending the cache?, Alex Sudakar
• WANTED new maintainer for Linux/md (and mdadm), NeilBrown
  • Re: WANTED new maintainer for Linux/md (and mdadm), Sebastian Parschauer
  • Re: WANTED new maintainer for Linux/md (and mdadm), Shaohua Li
    • Re: WANTED new maintainer for Linux/md (and mdadm), NeilBrown
  • Re: WANTED new maintainer for Linux/md (and mdadm), Brassow Jonathan
    • Re: WANTED new maintainer for Linux/md (and mdadm), Jes Sorensen
      • Re: WANTED new maintainer for Linux/md (and mdadm), NeilBrown
        • Re: WANTED new maintainer for Linux/md (and mdadm), Jes Sorensen
  • Re: WANTED new maintainer for Linux/md (and mdadm), Artur Paszkiewicz
    • Re: WANTED new maintainer for Linux/md (and mdadm), NeilBrown
      • Re: WANTED new maintainer for Linux/md (and mdadm), Jes Sorensen
• [RFC] zodcache - auto-start dm-cache devices, Ian Pilcher
  • Re: [RFC] zodcache - auto-start dm-cache devices, Joe Thornber
  • Re: [RFC] zodcache - auto-start dm-cache devices, John Stoffel
    • Re: [RFC] zodcache - auto-start dm-cache devices, Ian Pilcher
      • Re: [RFC] zodcache - auto-start dm-cache devices, Ian Pilcher
      • Re: [RFC] zodcache - auto-start dm-cache devices, John Stoffel
  • Re: [RFC] zodcache - auto-start dm-cache devices, Alasdair G Kergon
    • Re: [RFC] zodcache - auto-start dm-cache devices, John Stoffel
      • Re: [RFC] zodcache - auto-start dm-cache devices, Alasdair G Kergon
    • Re: [RFC] zodcache - auto-start dm-cache devices, Ian Pilcher
      • Re: [RFC] zodcache - auto-start dm-cache devices, Zdenek Kabelac
        • Re: [RFC] zodcache - auto-start dm-cache devices, Ian Pilcher
  • Never mind (was [RFC] zodcache - auto-start dm-cache devices), Ian Pilcher
    • Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices), John Stoffel
      • Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices), Joe Thornber
        • Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices), Ian Pilcher
• dm-cache selective promotion of block, Mahmoud Hanafi
  • Re: dm-cache selective promotion of block, Mike Snitzer
  • Re: dm-cache selective promotion of block, Joe Thornber
• [PATCH] dm-thin: Fix race condition when destroying thin pool, Nikolay Borisov
• [PATCH v2 0/6] Make blkdev_issue_discard() submit aligned discard requests, Bart Van Assche
  • [PATCH 1/6] block: Introduce blk_round_sect_down(), Bart Van Assche
    • Re: [PATCH 1/6] block: Introduce blk_round_sect_down(), Christoph Hellwig
  • [PATCH 3/6] block: Optimize __blkdev_issue_zeroout(), Bart Van Assche
    • Re: [PATCH 3/6] block: Optimize __blkdev_issue_zeroout(), Bart Van Assche
  • [PATCH 2/6] block: Introduce bio_add_zero_pages(), Bart Van Assche
    • Re: [PATCH 2/6] block: Introduce bio_add_zero_pages(), Christoph Hellwig
  • [PATCH 4/6] block: Make blkdev_issue_discard() submit aligned discard requests, Bart Van Assche
  • [PATCH 5/6] brd: Split bio if needed, Bart Van Assche
  • [PATCH 6/6] brd: Accept non-aligned discard requests with size zero, Bart Van Assche
• [PATCH v3 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
  • [PATCH v3 1/2] block: Introduce blk_bio_map_sg() to map one bio, Baolin Wang
  • [PATCH v3 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto, Baolin Wang
• Re: [PATCH 0/2] Fix blkdev_issue_discard(), Mike Snitzer
  • Re: [PATCH 0/2] Fix blkdev_issue_discard(), Jan Kara
    • Re: [PATCH 0/2] Fix blkdev_issue_discard(), Hannes Reinecke
  • Re: [PATCH 0/2] Fix blkdev_issue_discard(), Martin K. Petersen
• [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
  • [PATCH v2 1/2] block: Export the __blk_bios_map_sg() to map one bio, Baolin Wang
  • [PATCH v2 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto, Baolin Wang
  • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Milan Broz
    • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
    • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
      • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Milan Broz
        • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
        • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mark Brown
          • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Baolin Wang
          • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mikulas Patocka
            • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Arnd Bergmann
              • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mikulas Patocka
                • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Arnd Bergmann
                  • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mikulas Patocka
              • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Milan Broz
            • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mark Brown
              • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mikulas Patocka
                • Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency, Mark Brown
• linux-4.4-rc5 bug report ?, David Binderman
  • Re: linux-4.4-rc5 bug report ?, Mike Snitzer
• [PATCH 0/2] Optimize the dm-crypt for XTS mode, Baolin Wang
  • [PATCH 1/2] block: Export the __blk_bios_map_sg() to map one bio, Baolin Wang
  • [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode, Baolin Wang
    • Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode, Milan Broz
      • Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode, Baolin Wang
        • Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode, Milan Broz
          • Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode, Baolin Wang
• Re: : suggestion needed for dm-verity data block corrupted issue, Krishan Baveja
• [PATCH 0/15] copy offload patches, Mikulas Patocka
  • [PATCH 12/15] dm kcopyd: introduce the function submit_job, Mikulas Patocka
  • [PATCH 7/15] scsi xcopy: keep cache of failures, Mikulas Patocka
  • [PATCH 3/15] block copy: report the amount of copied data, Mikulas Patocka
  • [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock, Mikulas Patocka
  • [PATCH 1/15] block copy: initial XCOPY offload support, Mikulas Patocka
  • [PATCH 10/15] dm linear: support copy, Mikulas Patocka
  • [PATCH 13/15] dm kcopyd: support copy offload, Mikulas Patocka
  • [PATCH 9/15] dm: implement copy, Mikulas Patocka
  • [PATCH 14/15] dm kcopyd: change mutex to spinlock, Mikulas Patocka
  • [PATCH 8/15] block copy: introduce "copy_boundary" limits, Mikulas Patocka
  • [PATCH 6/15] scsi xcopy: suppress error messages, Mikulas Patocka
  • [PATCH 11/15] dm stripe: support copy, Mikulas Patocka
  • [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback, Mikulas Patocka
  • Re: [PATCH 0/15] copy offload patches, Martin K. Petersen
    • Re: [PATCH 0/15] copy offload patches, Mike Christie
      • Re: [PATCH 0/15] copy offload patches, Christoph Hellwig
    • Re: [PATCH 0/15] copy offload patches, Mikulas Patocka
      • Re: [PATCH 0/15] copy offload patches, Douglas Gilbert
      • Re: [PATCH 0/15] copy offload patches, Martin K. Petersen
  • [PATCH 5/15] block copy: use asynchronous notification, Mikulas Patocka
  • [PATCH 2/15] block copy: use two bios, Mikulas Patocka
• [dm-verity driver]: suggestion needed for dm-verity data block corrupted issue, Krishan Baveja
• [git pull] device mapper fixes for 4.4-rc5, Mike Snitzer
• 4.4-rc4 multipath not working?, E V
  • Re: 4.4-rc4 multipath not working?, Mike Snitzer
    • Re: 4.4-rc4 multipath not working?, E V
      • Re: 4.4-rc4 multipath not working?, Mike Snitzer
        • Re: 4.4-rc4 multipath not working?, Benjamin Marzinski
          • Re: 4.4-rc4 multipath not working?, E V
            • Re: 4.4-rc4 multipath not working?, Benjamin Marzinski
              • Re: 4.4-rc4 multipath not working?, E V
                • Re: 4.4-rc4 multipath not working?, Benjamin Marzinski
• Re: corruption causing crash in __queue_work, Tejun Heo
  • Re: corruption causing crash in __queue_work, Nikolay Borisov
    • Re: corruption causing crash in __queue_work, Mike Snitzer
      • Re: corruption causing crash in __queue_work, Nikolay Borisov
  • Re: corruption causing crash in __queue_work, Nikolay Borisov
    • Re: corruption causing crash in __queue_work, Mike Snitzer
      • Re: corruption causing crash in __queue_work, Nikolay Borisov
        • Re: corruption causing crash in __queue_work, Mike Snitzer
          • Re: corruption causing crash in __queue_work, Nikolay Borisov
            • Re: corruption causing crash in __queue_work, Tejun Heo
              • Re: corruption causing crash in __queue_work, Nikolay Borisov
                • Re: corruption causing crash in __queue_work, Tejun Heo
                  • Re: corruption causing crash in __queue_work, Mike Snitzer
                    • Re: corruption causing crash in __queue_work, Nikolay Borisov
                      • Re: corruption causing crash in __queue_work, Tejun Heo
                        • Re: corruption causing crash in __queue_work, Tejun Heo
• fixing mangled UUIDs, John Stoffel
  • Re: fixing mangled UUIDs, Alasdair G Kergon
    • Re: fixing mangled UUIDs, John Stoffel
      • Re: fixing mangled UUIDs, Zdenek Kabelac
        • Re: fixing mangled UUIDs, John Stoffel
          • Re: fixing mangled UUIDs, Zdenek Kabelac
            • Re: [linux-lvm] fixing mangled UUIDs, John Stoffel
              • Re: [linux-lvm] fixing mangled UUIDs, Zdenek Kabelac
• [PATCH] dm verity: use sector_div for division, Arnd Bergmann
  • Re: dm verity: use sector_div for division, Mike Snitzer
• [PATCH v2 00/19] Support fuse mounts in user namespaces, Seth Forshee
  • [PATCH v2 06/18] Smack: Handle labels consistently in untrusted mounts, Seth Forshee
  • [PATCH v2 08/18] cred: Reject inodes with invalid ids in set_create_file_as(), Seth Forshee
  • [PATCH v2 05/18] userns: Replace in_userns with current_in_userns, Seth Forshee
  • [PATCH v2 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns, Seth Forshee
  • [PATCH v2 01/18] block_dev: Support checking inode permissions in lookup_bdev(), Seth Forshee
  • [PATCH v2 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns, Seth Forshee
  • [PATCH v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes, Seth Forshee
  • [PATCH v2 07/18] fs: Check for invalid i_uid in may_follow_link(), Seth Forshee
  • [PATCH v2 14/18] capabilities: Allow privileged user in s_user_ns to set security.* xattrs, Seth Forshee
  • [PATCH v2 04/18] selinux: Add support for unprivileged mounts from user namespaces, Seth Forshee
  • [PATCH v2 02/18] block_dev: Check permissions towards block device inode when mounting, Seth Forshee
  • [PATCH v2 18/18] fuse: Allow user namespace mounts, Seth Forshee
  • [PATCH v2 16/18] fuse: Support fuse filesystems outside of init_user_ns, Seth Forshee
  • [PATCH v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant, Seth Forshee
  • [PATCH v2 03/18] fs: Treat foreign mounts as nosuid, Seth Forshee