Linux RAID Storage Date Index

• Thread Index

• Re: Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot)
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] util: fix wrong return value of cluster_get_dlmlock
  • From: NeilBrown <neilb@xxxxxxx>
• RAID journal, requirements?
  • From: Linus Lüssing <linus.luessing@xxxxxxxxx>
• Re: Uneven wear on raid1 devices
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Uneven wear on raid1 devices
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot)
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: md127 auto created when use "-B" to build a legacy array without superblocks
  • From: NeilBrown <neilb@xxxxxxxx>
• Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot)
  • From: Eric Valette <Eric.Valette@xxxxxxx>
• Re: md127 auto created when use "-B" to build a legacy array without superblocks
  • From: yizhan <yizhan@xxxxxxxxxx>
• Re: [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: Chien Lee <chienlee@xxxxxxxx>
• 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: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH RESEND v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: Uneven wear on raid1 devices
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: Uneven wear on raid1 devices
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Uneven wear on raid1 devices
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md-cluster: delete useless code
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/2] md-cluster: fix missing memory free
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: md failing mechanism
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: James J <james.j@xxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Wrong device name after hot-swap
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: Wrong device name after hot-swap
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 1/2] md-cluster: fix missing memory free
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/2] md-cluster: delete useless code
  • From: Shaohua Li <shli@xxxxxx>
• Re: md failing mechanism
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md failing mechanism
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: md failing mechanism
  • From: James J <james.j@xxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: Wrong device name after hot-swap
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: md failing mechanism
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: Wrong device name after hot-swap
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md failing mechanism
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Wrong device name after hot-swap
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: md failing mechanism
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md failing mechanism
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• md failing mechanism
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: [PATCH] raid6/algos.c : bug fix : Add the missing definitions to the pq.h file
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] raid6/algos.c : bug fix : Add the missing definitions to the pq.h file
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• Re: Intel IMSM RAID 5 won't start - now jbd2 blocked for more than 120 seconds
  • From: "Guido D'Arezzo" <gdarrezzo@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH] util: fix wrong return value of cluster_get_dlmlock
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] Abort pending request for RAID10
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: ICH RAID5 delisted and broken after mdadm installation
  • From: Пётр Б. <satnatantas@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Help with RAID data recovery.
  • From: Tommy Wang <lists@xxxxxxxxxxx>
• Re: [PATCH] Abort pending request for RAID10
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH] Abort pending request for RAID10
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: ICH RAID5 delisted and broken after mdadm installation
  • From: Пётр Б. <satnatantas@xxxxxxxxx>
• ICH RAID5 delisted and broken after mdadm installation
  • From: Пётр Б. <satnatantas@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [GIT PULL REQUEST] md updates for 4.5
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: writeback: Stability issue (BUG) on 4.4 with writeback_percent
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• scsi_debug support
  • From: Tejas Rao <raot@xxxxxxx>
• Add. Sense: Data synchronization mark error
  • From: Tejas Rao <raot@xxxxxxx>
• Re: [PATCH V2 2/2] Add casts for the addr arg of connect and bind
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: mdadm Oops on a small ARM system
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• mdadm Oops on a small ARM system
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• [PATCH V2 2/2] Add casts for the addr arg of connect and bind
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• [PATCH V2 1/2] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• Re: [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• Re: [PATCH] md/raid: only permit hot-add of compatible integrity profiles
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• [PATCH] md/raid: only permit hot-add of compatible integrity profiles
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• [PATCH] Define _POSIX_C_SOURCE if undefined
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [dm-devel] [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] Fix wrong description in manpage
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Fix wrong description in manpage
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/35] fs: have submit_bh users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/35] direct-io: 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 09/35] btrfs: update __btrfs_map_block for bi_op transition
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/35] f2fs: set bi_op to REQ_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 13/35] xfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/35] mpage: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/35] hfsplus: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/35] ocfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/35] nilfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/35] pm: 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 21/35] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/35] dm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/35] md/raid: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/35] xen: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/35] drbd: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/35] block: set op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/35] target: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/35] drivers: set request op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/35] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/35] blktrace: get op from req->op/bio->bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/35] block: shrink bi_rw and bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/35] block, fs: remove old REQ definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• Re: Intel IMSM RAID 5 won't start
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [dm-devel] [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>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • 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: [dm-devel] 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: WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: stripe_cache_active always 0
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: stripe_cache_active always 0
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• RE: stripe_cache_active always 0
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: [PATCH] async_tx: use GFP_NOWAIT rather than GFP_IO
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• stripe_cache_active always 0
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• 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: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 1/3] md: set MD_HAS_JOURNAL in correct places
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] imsm: use timeout when waiting for reshape progress
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• [PATCH] async_tx: use GFP_NOWAIT rather than GFP_IO
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH 2/3] MD: add journal with array suspended
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 3/3] raid5-cache: handle journal hotadd in quiesce
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/3] md: set MD_HAS_JOURNAL in correct places
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 25/35] target: set bi_op to REQ_OP
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: Vinod Koul <vinod.koul@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 3/4] raid5-cache: handle flush request for journal hotadd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] raid5-cache: correctly handle stripe with enough journal space
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 2/2] raid5-cache: correctly handle stripe with enough journal space
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] raid5-cache: destroy mempool
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] raid5-cache: handle flush request for journal hotadd
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] IMSM: Add support for VMD
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] raid5-cache: handle flush request for journal hotadd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/4] raid5-cache: use rcu api to access r5conf->log
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/4] raid5-cache: avoid write failure for journal hotadd
  • From: NeilBrown <neilb@xxxxxxx>
• 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>
• [PATCH 4/4] raid5-cache: handle batch stripe for journal hotadd
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/4] raid5-cache: use rcu api to access r5conf->log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/4] raid5-cache: avoid write failure for journal hotadd
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/4]raid5-cache: fix journal hotadd
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 3/4] raid5-cache: handle flush request for journal hotadd
  • From: Shaohua Li <shli@xxxxxx>
• [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 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/35] direct-io: set bi_op to REQ_OP
  • 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 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/35] btrfs: set bi_op tp REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/35] block, fs, mm, drivers: 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 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 14/35] hfsplus: set bi_op to REQ_OP
  • 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 17/35] ocfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/35] dm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/35] pm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/35] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/35] drbd: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/35] md/raid: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/35] xen: 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 25/35] target: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/35] drivers: set request op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/35] blktrace: get op from req->op/bio->bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/35] block: set op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/35] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/35] block: shrink bi_rw and bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/35] block, fs: remove old REQ definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/35] f2fs: 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 2/2] imsm: don't update migration record when reshape is interrupted
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 1/2] imsm: use timeout when waiting for reshape progress
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH] IMSM: Add support for VMD
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: Reading the same block via partition and non-partitioned device gives different content
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• [patch -next] bcache: cleanup indenting in bch_btree_insert_check_key()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Reading the same block via partition and non-partitioned device gives different content
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• [PATCH 2/2] raid5-cache: correctly handle stripe with enough journal space
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/2] raid5-cache: destroy mempool
  • From: Shaohua Li <shli@xxxxxx>
• Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH RESEND v2 01/18] block_dev: Support checking inode permissions in lookup_bdev()
  • 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 00/19] Support fuse mounts in 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 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • 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 06/18] Smack: Handle labels consistently in untrusted mounts
  • 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 15/18] fuse: Add support for pid namespaces
  • 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 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • 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 08/18] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND v2 10/18] fs: Update posix_acl support to handle user namespace mounts
  • 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 03/18] fs: Treat foreign mounts as nosuid
  • 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 05/18] userns: Replace in_userns with current_in_userns
  • 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>
• Re: raid5 async_xor: sleep in atomic
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Intel IMSM RAID 5 won't start
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Intel IMSM RAID 5 won't start
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [dm-devel] 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: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: remove unnecesary md_new_event_inintr
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: NeilBrown <neilb@xxxxxxxx>
• Intel IMSM RAID 5 won't start
  • From: "Guido D'Arezzo" <gdarrezzo@xxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Problems reassembling raid6 with --force option
  • From: René <rk@xxxxxxxxx>
• Re: Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• raid5d hangs when stopping an array during reshape
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: Stanislav Samsonov <slava@xxxxxxxxxxxxxxxxx>
• [PATCH] md: remove unnecesary md_new_event_inintr
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Recreating RAID-5 after SATA controller failure and botched auto-assemble
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• [PATCH v5 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v5 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [GIT PULL REQUEST] one more md fix for 4.4-rc
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/2] imsm: abort reshape if sync_action is not "reshape"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] Grow: close file descriptor earlier to avoid "still in use" when stopping
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID10 Write Performance
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• RE: Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Create Lock to Eliminate RMW in RAID/456 when writing perfect stripes
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: RAID10 Write Performance
  • From: Marc Smith <marc.smith@xxxxxxx>
• [PATCH 2/2] imsm: abort reshape if sync_action is not "reshape"
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 1/2] Grow: close file descriptor earlier to avoid "still in use" when stopping
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Recreating RAID-5 after SATA controller failure and botched auto-assemble
  • From: Wolfgang Draxinger <wdraxinger.maillist@xxxxxxxxx>
• Re: raid5 async_xor: sleep in atomic
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID10 Write Performance
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/2] md: Replace get_seconds with ktime_get_seconds
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH 2/2] md: Replace get_seconds with ktime_get_seconds
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: RAID10 Write Performance
  • From: Marc Smith <marc.smith@xxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Christoph Hellwig <hch@xxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [PATCH v2 1/2] md: bcache: Replace get_seconds with ktime_get_seconds
  • From: Shraddha Barke <shraddha.6596@xxxxxxxxx>
• [PATCH 2/2] md: Replace get_seconds with ktime_get_seconds
  • From: Shraddha Barke <shraddha.6596@xxxxxxxxx>
• raid5 async_xor: sleep in atomic
  • From: Stanislav Samsonov <slava@xxxxxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [MDADM PATCH] Check and remove bitmap first when reshape to raid0
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• [MDADM PATCH] Check and remove bitmap first when reshape to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Tejas Rao <raot@xxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Aaron Knister <aaron.s.knister@xxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Tejas Rao <raot@xxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Tejas Rao <raot@xxxxxxx>
• Re: [MDADM PATCH] Check and remove bitmap first when reshape to raid0
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/3] Add new journal to array that does not have journal
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: Tejas Rao <raot@xxxxxxx>
• [PATCH 3/3] Add new journal to array that does not have journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/3] [mdadm] fixes and feature for journal device
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/3] [mdadm] move journal to end of --detail list
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 2/3] [mdadm] in --add assign raid_disk of 0 to journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: WANTED new maintainer for Linux/md (and mdadm)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [MDADM PATCH] Check and remove bitmap first when reshape to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• WANTED new maintainer for Linux/md (and mdadm)
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Stop resync operation
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: RESYNC Bug ? [was Re: Stop resync operation]
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: badblocks seem to be causing problems with raid6 - badblocks list replicating all all drives
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: mdadm and size differences
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: Seeking advice to convert RAID5 to RAID10 adding a drive in the process
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: Start reshape failed
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: Problem w/ commit ac8fa4196d20 on older, slower hardware
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: clustered MD - beyond RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID6 - whole disk vs partitions
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• [GIT PULL REQUEST] md fixes for 4.4-rc
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID6 - whole disk vs partitions
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RAID6 - whole disk vs partitions
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Shaohua Li <shli@xxxxxx>
• RAID10 Write Performance
  • From: Marc Smith <marc.smith@xxxxxxx>
• clustered MD - beyond RAID1
  • From: Scott Sinno <scott.sinno@xxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] Fix remove_and_add_spares removes drive added as spare in slot_store
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Shaohua Li <shli@xxxxxx>
• Re: raid5-cache: avoid GFP_NOFAIL allocation
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 3/3] raid5: allow r5l_io_unit allocations to fail
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/3] raid5-cache: use a mempool for the metadata block
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/3] raid5-cache: use a bio_set
  • From: Christoph Hellwig <hch@xxxxxx>
• raid5-cache: avoid GFP_NOFAIL allocation
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH] Fix remove_and_add_spares removes drive added as spare in slot_store
  • From: rgoldwyn@xxxxxxx
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • 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 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto
  • 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: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 2/2] mdadm: improve the safeguard for change cluster raid's sb
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/2] raid5-cache: add journal hot add/remove support
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 1/2] MD: change journal disk role to disk 0
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/2] raid5-cache: add journal hot add/remove support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH 2/2] mdadm: improve the safeguard for change cluster raid's sb
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/2] mdadm: do not try to hold dlm lock in free_super1
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• 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: Start reshape failed
  • From: Kev Dorman <kdorman036@xxxxxxxxx>
• Re: [PATCH] drivers: md: use ktime_get_real_seconds()
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: avoid warning for 32-bit sector_t
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: NeilBrown <neilb@xxxxxxx>
• [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>
• [PATCH v2 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 4/4] mdadm: do not display bitmap info if it is cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 0/2] mdadm: re-add journal to array with bad journal
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] md/raid10: fix data corruption and crash during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: core dump on initial sync of raid10 please help
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] raid5-cache: add journal hot add/remove support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH v2 2/2] [mdadm] recreate journal in mdadm
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 1/2] add sysfs_array_state to struct mdinfo
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 0/2] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: core dump on initial sync of raid10 please help
  • From: "Micheal Blue" <mblue@xxxxxx>
• Re: [PATCH] md/raid10: fix data corruption and crash during resync
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• core dump on initial sync of raid10 please help
  • From: "Micheal Blue" <mblue@xxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• [PATCH 0/2] 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 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Seeking advice to convert RAID5 to RAID10 adding a drive in the process
  • From: "Micheal Blue" <mblue@xxxxxx>
• Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• RE: [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 2/2] raid5-cache: use a mempool for the metadata block
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: two small raid5 cache updates
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 2/2] md: update comment for md_allow_write
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] [mdadm] fix bug in assemble
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH v4 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• 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: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Andrew Wilkins <andrew.m.wilkins@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v2 0/3] Badblock tracking for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Help Reassembling a raid5 array
  • From: Andrew Wilkins <andrew.m.wilkins@xxxxxxxxx>
• RE: [PATCH 1/2] [mdadm] fix bug in assemble
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] [mdadm] fix bug in assemble
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 01/18] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 00/19] Support fuse mounts in user namespaces
  • 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 05/18] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 03/18] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 06/18] Smack: Handle labels consistently in untrusted mounts
  • 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 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns
  • 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 10/18] fs: Update posix_acl support to handle user namespace mounts
  • 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 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • 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 18/18] fuse: Allow user namespace mounts
  • 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 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 04/18] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: David Waite <david@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: David Waite <david@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• 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 v2 2/3] block: Add badblock management for gendisks
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• 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/3] Badblock tracking for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• 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 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • 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 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • 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 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@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 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_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@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: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • From: "Serge E. Hallyn" <serge@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 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 10/19] fs: Update posix_acl support to handle user namespace mounts
  • From: "Serge E. Hallyn" <serge@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: RAID6 - "Invalid Argument" / "does not have a valid v1.2 superblock" ?!
  • From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
• 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 05/19] userns: Replace in_userns with current_in_userns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: "Serge E. Hallyn" <serge.hallyn@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 07/19] fs: Check for invalid i_uid in may_follow_link()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/2] md: update comment for md_allow_write
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: Shaohua Li <shli@xxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: two small raid5 cache updates
  • From: Shaohua Li <shli@xxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• RAID6 - "Invalid Argument" / "does not have a valid v1.2 superblock" ?!
  • From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
• [PATCH 2/2] raid5-cache: use a mempool for the metadata block
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/2] raid5-cache: use a bio_set
  • From: Christoph Hellwig <hch@xxxxxx>
• [RFC] using mempools for raid5-cache
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/2] raid5-cache: free meta_page earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/2] raid5-cache: simplify r5l_move_io_unit_list
  • From: Christoph Hellwig <hch@xxxxxx>
• two small raid5 cache updates
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 06/19] Smack: Handle labels consistently in untrusted mounts
  • 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 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 10/19] fs: Update posix_acl support to handle 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 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • 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 12/19] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • 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 19/19] fuse: Allow user namespace mounts
  • 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 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 16/19] fuse: Add support for pid namespaces
  • 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>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: keld@xxxxxxxxxx
• [PATCH 2/3] [mdadm] recreate journal in mdadm
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/3] add sysfs_array_state to struct mdinfo
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 16/17] Clear MBR in when Kill superblock
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 11/17] policy: enable enclosure names for domain definitions
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 02/17] mdadm: allow a /dev/disk/by-slot as domain path descriptor
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 10/17] config: ENCLOSURE keyword and enclosure device list expansion
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 15/17] SCSIMODE: configuration file support for mode page settings.
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 06/17] ses: workaround sysfs deprecated
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 17/17] In generated udev rules, skip RAID members
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 05/17] imsm: quiet detail platform
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 12/17] invoke hot-add policy on "change" events
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 14/17] scsi mode sense/select support
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 01/17] udev rules and infrastructure for /dev/disk/by-slot
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 04/17] fix variable offset when ':' is present in the device name
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 08/17] enclosure detection/enumeration
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 13/17] Toggle enclosure leds in response to raid events
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 03/17] 'act_spare' should be the minimum requirement for dynamic domains
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 07/17] prepare for enclosure platform details
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 09/17] Add --brief support to --enclosure
  • From: Song Liu <songliubraving@xxxxxx>
• RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: Shaohua Li <shli@xxxxxxxxxx>