Linux Device-Mapper Development

• Thread Index

• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 17/26] mac802154: Use skcipher
  • From: Stefan Schmidt <stefan@xxxxxxxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: LVM thin provisioning actual status
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• LVM thin provisioning actual status
  • From: Никифоров Руслан <nikiforovr@xxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 22/26] iscsi_tcp: Use ahash
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: Can anyone help me understand what is going wrong with a dm-multipah config I have?
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• Re: [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Julia Lawall <julia.lawall@xxxxxxx>
• Re: [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH 26/26] tcp: Use ahash
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 25/26] sctp: Use shash
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [v2 PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash
  • From: Greg KH <greg@xxxxxxxxx>
• [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 22/26] iscsi_tcp: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 10/26] ext4: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 26/26] tcp: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 14/26] KEYS: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 23/26] iscsi-target: Use shash and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 2/26] ppp_mppe: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 5/26] orinoco: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 18/26] rxrpc: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 25/26] sctp: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 4/26] dm crypt: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 11/26] f2fs: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 24/26] nfsd: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 13/26] lib80211: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 21/26] nfc: s3fwrn5: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 20/26] drbd: Use shash and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 0/26] crypto: Use skcipher and ahash/shash where possible
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 12/26] sunrpc: Use skcipher and ahash/shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 17/26] mac802154: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 8/26] cifs: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 7/26] wusb: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 24/26] nfsd: Use shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 21/26] nfc: s3fwrn5: Use shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 4/26] dm crypt: Use skcipher and ahash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 7/26] wusb: Use skcipher
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2] dm pref-path: provides preferred path load balance policy
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v2] dm pref-path: provides preferred path load balance policy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH v2] dm pref-path: provides preferred path load balance policy
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• [PATCH v2] dm pref-path: provides preferred path load balance policy
  • From: Ravikanth Nalla <ravikanth.nalla@xxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-cache + storage client experiment
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: How can I get my sector size (via queue_limits?) from a dm_target?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH V2] kpartx: support device names with spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: dm-cache + storage client experiment
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH V2] kpartx: support device names with spaces
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] kpartx: support device names with spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• [PATCH V2] kpartx: support device names with spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: I/O block when removing thin device on the same pool
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• dm-cache + storage client experiment
  • From: "mlody3k ." <mlody3k@xxxxxxxxx>
• I/O block when removing thin device on the same pool
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• Re: [PATCH] kpartx: support device names with spaces
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• How can I get my sector size (via queue_limits?) from a dm_target?
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: How can dm use limits.max_hw_sectors from the bdev?
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Question about multipath device compiled defaults
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: dm-multipath low performance with blk-mq
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: device mapper increased latency on RAID array
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: How can need dm use limits.max_hw_sectors from the bdev?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: device mapper increased latency on RAID array
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• How can need dm use limits.max_hw_sectors from the bdev?
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: device mapper increased latency on RAID array
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: device mapper increased latency on RAID array
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits"
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits"
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Add. Sense: Data synchronization mark error
  • From: Tejas Rao <raot@xxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• getting support for PURE FlashArray into multipath-tools
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• [PATCH RESEND] md:Check if call to thaw_bdev fails in unlock_fs
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• device mapper increased latency on RAID array
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH v2] dm stripe: document that chunk size is specified in sectors (resend)
  • From: Tomohiro Kusumi <kusumi.tomohiro@xxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits"
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits"
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• 4.4 regression/bisected: error message due to "block/sd: Fix device-imposed transfer length limits"
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] dm stripe: document that chunk size is specified in sectors (resend)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm stripe: document that chunk size is specified in sectors (resend)
  • From: kusumi.tomohiro@xxxxxxxxx
• [PATCH 2/2] dm flakey: document that default I/O error is only for write (resend)
  • From: kusumi.tomohiro@xxxxxxxxx
• [PATCH 08/35] btrfs: set bi_op tp REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/35] drivers: set request op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/35] hfsplus: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/35] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/35] drbd: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 20/35] dm: pass dm stats data dir instead of bi_rw
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/35] xen: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/35] md/raid: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/35] block, fs: remove old REQ definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/35] target: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/35] blktrace: get op from req->op/bio->bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/35] dm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/35] block: shrink bi_rw and bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/35] block: set op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/35] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/35] direct-io: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/35] mpage: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/35] ocfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/35] fs: have submit_bh users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/35] f2fs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/35] pm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 09/35] btrfs: update __btrfs_map_block for bi_op transition
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/35] nilfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/35] block, fs, mm, drivers: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 12/35] gfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 13/35] xfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: mchristi@xxxxxxxxxx
• [git pull] device mapper changes for 4.5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC] disk doesn't spin down with thin pool + dmeventd
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [RFC] disk doesn't spin down with thin pool + dmeventd
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [RFC] disk doesn't spin down with thin pool + dmeventd
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 26/35] block: set op to REQ_OP
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 2/2] dm-snapshot: merge functions commit_callback and pending_complete
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm-snapshot: fix hung bios when copy error happens
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• please pull in commit 0fcb04d59351f to stable@ 4.1+
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC] disk doesn't spin down with thin pool + dmeventd
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [RFC] disk doesn't spin down with thin pool + dmeventd
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] kpartx: support device names with spaces
  • From: Mauricio Faria de Oliveira <mauricfo@xxxxxxxxxxxxxxxxxx>
• Re: dm ioctl: Access user-land memory through safe functions.
  • From: Scotty Bauer <sbauer@xxxxxxxxxxxx>
• Re: [PATCH 25/35] target: set bi_op to REQ_OP
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 13/35] xfs: set bi_op to REQ_OP
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: dm ioctl: Access user-land memory through safe functions.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• can't boot with linux-next-20160104
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices)
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: dm ioctl: Access user-land memory through safe functions.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 31/35] block, fs: remove old REQ definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/35] drbd: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/35] dm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/35] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/35] f2fs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 09/35] btrfs: update __btrfs_map_block for bi_op transition
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/35] md/raid: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/35] block: shrink bi_rw and bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/35] blktrace: get op from req->op/bio->bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/35] block: set op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/35] xen: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/35] drivers: set request op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/35] target: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/35] fs: have submit_bh users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/35] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/35] direct-io: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/35] ocfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/35] block, fs, mm, drivers: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 13/35] xfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/35] btrfs: set bi_op tp REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 12/35] gfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 20/35] dm: pass dm stats data dir instead of bi_rw
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/35] mpage: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/35] nilfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/35] hfsplus: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/35] pm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• Re: dm ioctl: Access user-land memory through safe functions.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH RESEND v2 10/18] fs: Update posix_acl support to handle user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 16/18] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 14/18] capabilities: Allow privileged user in s_user_ns to set security.* xattrs
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 04/18] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 06/18] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RESEND v2 08/18] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 13/18] fs: Allow superblock owner to access do_remount_sb()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 15/18] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 05/18] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 18/18] fuse: Allow user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 03/18] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 02/18] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 07/18] fs: Check for invalid i_uid in may_follow_link()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 01/18] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices)
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache: Can I change policy without suspending the cache?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• dm-cache: Can I change policy without suspending the cache?
  • From: Alex Sudakar <alex.sudakar@xxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Tejun Heo <tj@xxxxxxxxxx>
• WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: Never mind (was [RFC] zodcache - auto-start dm-cache devices)
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Never mind (was [RFC] zodcache - auto-start dm-cache devices)
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH 1/6] block: Introduce blk_round_sect_down()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 2/6] block: Introduce bio_add_zero_pages()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dm-cache selective promotion of block
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [RFC] zodcache - auto-start dm-cache devices
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [RFC] zodcache - auto-start dm-cache devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: dm-cache selective promotion of block
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache selective promotion of block
  • From: Mahmoud Hanafi <mahmoud.hanafi@xxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-thin: Fix race condition when destroying thin pool
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 3/6] block: Optimize __blkdev_issue_zeroout()
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 6/6] brd: Accept non-aligned discard requests with size zero
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 5/6] brd: Split bio if needed
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 4/6] block: Make blkdev_issue_discard() submit aligned discard requests
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 2/6] block: Introduce bio_add_zero_pages()
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 3/6] block: Optimize __blkdev_issue_zeroout()
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH 1/6] block: Introduce blk_round_sect_down()
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH v2 0/6] Make blkdev_issue_discard() submit aligned discard requests
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v3 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v3 1/2] block: Introduce blk_bio_map_sg() to map one bio
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v3 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH] md: fix bug due to nested suspend
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 0/2] Fix blkdev_issue_discard()
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] md: fix bug due to nested suspend
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/2] Fix blkdev_issue_discard()
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 0/2] Fix blkdev_issue_discard()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 0/2] Fix blkdev_issue_discard()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] md: fix bug due to nested suspend
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH v2 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v2 1/2] block: Export the __blk_bios_map_sg() to map one bio
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: E V <eliventer@xxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: E V <eliventer@xxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: E V <eliventer@xxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: linux-4.4-rc5 bug report ?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• linux-4.4-rc5 bug report ?
  • From: David Binderman <dcb314@xxxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 1/2] block: Export the __blk_bios_map_sg() to map one bio
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 0/2] Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: : suggestion needed for dm-verity data block corrupted issue
  • From: Krishan Baveja <kkbaveja1@xxxxxxxxx>
• [PATCH 2/15] block copy: use two bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/15] copy offload patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [dm-verity driver]: suggestion needed for dm-verity data block corrupted issue
  • From: Krishan Baveja <kkbaveja1@xxxxxxxxx>
• Re: fixing mangled UUIDs
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: lvremove kernel BUG at drivers/md/dm-bufio.c:1494!
  • From: Nikolay Borisov <n.borisov@xxxxxxxxxxxxxx>
• Re: 4.4-rc4 multipath not working?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 4.4-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• 4.4-rc4 multipath not working?
  • From: E V <eliventer@xxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: corruption causing crash in __queue_work
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH 5/15] block copy: use asynchronous notification
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 0/15] copy offload patches
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [linux-lvm] fixing mangled UUIDs
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 11/15] dm stripe: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/15] scsi xcopy: suppress error messages
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/15] block copy: introduce "copy_boundary" limits
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 14/15] dm kcopyd: change mutex to spinlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 9/15] dm: implement copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 13/15] dm kcopyd: support copy offload
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 10/15] dm linear: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/15] block copy: report the amount of copied data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/15] scsi xcopy: keep cache of failures
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 12/15] dm kcopyd: introduce the function submit_job
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [linux-lvm] fixing mangled UUIDs
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: fixing mangled UUIDs
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: fixing mangled UUIDs
  • From: Zdenek Kabelac <zdenek.kabelac@xxxxxxxxx>
• Re: fixing mangled UUIDs
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: fixing mangled UUIDs
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• fixing mangled UUIDs
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] dm ioctl: Access user-land memory through safe functions.
  • From: Scotty Bauer <sbauer@xxxxxxxxxxxx>
• Re: dm verity: use sector_div for division
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm verity: use sector_div for division
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH v2 10/18] fs: Update posix_acl support to handle user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 15/18] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 13/18] fs: Allow superblock owner to access do_remount_sb()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 03/18] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 16/18] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 18/18] fuse: Allow user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 02/18] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 04/18] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 14/18] capabilities: Allow privileged user in s_user_ns to set security.* xattrs
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 07/18] fs: Check for invalid i_uid in may_follow_link()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 01/18] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 05/18] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 08/18] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 06/18] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH 07/19] fs: Check for invalid i_uid in may_follow_link()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 10/19] fs: Update posix_acl support to handle user namespace mounts
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 05/19] userns: Replace in_userns with current_in_userns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 12/19] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 08/19] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• [PATCH] dm-writecache target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Modern device mapper module makes problems for dump analysis
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/2] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Modern device mapper module makes problems for dump analysis
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm pref-path: provides preferred path load balance policy
  • From: Ravikanth Nalla <ravikanth.nalla@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2 1/2] dm verity: add support for forward error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH v2 2/2] dm verity: ignore zero blocks
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH v2 0/2] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Sami Tolvanen <samitolvanen@xxxxxxxxxx>
• [PATCH 16/19] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 06/19] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 12/19] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 10/19] fs: Update posix_acl support to handle user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 19/19] fuse: Allow user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 08/19] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 04/19] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 05/19] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 07/19] fs: Check for invalid i_uid in may_follow_link()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm:for-next 11/11] drivers/md/dm-verity.c:737:31: warning: passing argument 2 of 'dm_read_arg_group' from incompatible pointer type
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [dm:for-next 11/11] drivers/md/dm-verity.c:737:31: warning: passing argument 2 of 'dm_read_arg_group' from incompatible pointer type
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/4] dm verity: separate function for parsing opt args
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm snapshot: improve documentation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH] dm ioctl: Access user-land memory through safe functions.
  • From: Scotty <sbauer@xxxxxxxxxxxx>
• [RFC] Modern device mapper module makes problems for dump analysis
  • From: Alexey Ishchuk <aishchuk@xxxxxxxxxxxxxxxxxx>
• [PATCH] dm: constify crypt_iv_operations structures
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• Re: [PATCH] dm-ioctl: fix 4-characters indentations
  • From: Minfei Huang <mnfhuang@xxxxxxxxx>
• Re: dm: don't save and restore bi_private
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: don't save and restore bi_private
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: don't save and restore bi_private
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-ioctl: fix 4-characters indentations
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: dm: don't save and restore bi_private
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: don't save and restore bi_private
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] md: fix bug due to nested suspend
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] md: dm-bufio: Use BUG_ON instead of if BUG
  • From: Anup Limbu <anuplimbu14@xxxxxxxxx>
• [git pull] device mapper fixes for 4.4-rc3
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Adding new resiliency type to LVM
  • From: Shehbaz Jaffer <shehbazjaffer007@xxxxxxxxx>
• [PATCH] dm-bufio: store stacktrace in the buffers
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-block-manager: stacktrace cleanup
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-bufio: code cleanup - return NULL, not b
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• dm-cache metadata size questions
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: lvremove kernel BUG at drivers/md/dm-bufio.c:1494!
  • From: Marian Marinov <mm@xxxxxxxxxxxxxx>
• 4.4-rc1 dm-mpath infinite loop
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: lvremove kernel BUG at drivers/md/dm-bufio.c:1494!
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Adding new resiliency type to LVM
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• lvremove kernel BUG at drivers/md/dm-bufio.c:1494!
  • From: vaLentin chernoZemski <valentin@xxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Colin Walters <walters@xxxxxxxxxx>
• Adding new resiliency type to LVM
  • From: Shehbaz Jaffer <shehbazjaffer007@xxxxxxxxx>
• Re: [PATCH 1/2] dm mpath: fix infinite recursion in ioctl when no paths and queue_if_no_path is not set
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm-crypt: fix a possible race condition on exit
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Kernel BUG at dm-cache-policy-mq.c
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] dm-crypt: fix a possible race condition on exit
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Serge Hallyn <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 1/2] dm mpath: fix infinite recursion in ioctl when no paths and queue_if_no_path is not set
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH] dm-crypt: fix a possible race condition on exit
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• [PATCH 1/2] dm stripe: document that chunk size is specified in sectors
  • From: Tomohiro Kusumi <kusumi.tomohiro@xxxxxxxxx>
• [PATCH 2/2] dm flakey: document that default I/O error is only for write
  • From: Tomohiro Kusumi <kusumi.tomohiro@xxxxxxxxx>
• Can anyone help me understand what is going wrong with a dm-multipah config I have?
  • From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 4/7] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 1/7] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• [PATCH v3 6/7] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 2/7] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v3 3/7] mtd: Check permissions towards mtd block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 6/7] userns: Replace in_userns with current_in_userns
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 4/7] fs: Treat foreign mounts as nosuid
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 2/4] dm verity: separate function for parsing opt args
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 1/4] dm verity: clean up duplicate hashing code
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] dm: fix ioctl retry termination with signal
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• [PATCH 1/2] dm mpath: fix infinite recursion in ioctl when no paths and queue_if_no_path is not set
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: dm-multipath test scripts
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: dm-multipath test scripts
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/4] dm verity: add support for error correction
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 2/2] md: dm-crypt: Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>