summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid5.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-03-19 02:46:38 +0100
committerNeilBrown <neilb@suse.de>2012-03-19 02:46:38 +0100
commitd6b42dcb995e6acd7cc276774e751ffc9f0ef4bf (patch)
treea9112351e8ddd2866afd8687b645a1c5bf574ee7 /drivers/md/raid5.c
parentmd/bitmap: ensure to load bitmap when creating via sysfs. (diff)
downloadlinux-d6b42dcb995e6acd7cc276774e751ffc9f0ef4bf.tar.xz
linux-d6b42dcb995e6acd7cc276774e751ffc9f0ef4bf.zip
md/raid1,raid10: avoid deadlock during resync/recovery.
If RAID1 or RAID10 is used under LVM or some other stacking block device, it is possible to enter a deadlock during resync or recovery. This can happen if the upper level block device creates two requests to the RAID1 or RAID10. The first request gets processed, blocks recovery and queue requests for underlying requests in current->bio_list. A resync request then starts which will wait for those requests and block new IO. But then the second request to the RAID1/10 will be attempted and it cannot progress until the resync request completes, which cannot progress until the underlying device requests complete, which are on a queue behind that second request. So allow that second request to proceed even though there is a resync request about to start. This is suitable for any -stable kernel. Cc: stable@vger.kernel.org Reported-by: Ray Morris <support@bettercgi.com> Tested-by: Ray Morris <support@bettercgi.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid5.c')
0 files changed, 0 insertions, 0 deletions