summaryrefslogtreecommitdiff
path: root/drivers/md/Kconfig
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2013-02-25 01:38:29 (GMT)
committerNeilBrown <neilb@suse.de>2013-02-26 00:58:50 (GMT)
commitee0b0244030434cdda26777bfb98962447e080cd (patch)
treef2e59eeed60c0b76f6f53c63221114f2c0d3dbe2 /drivers/md/Kconfig
parentf96c9f305c24a0d4a075e2c75aa6b417aa238687 (diff)
downloadlinux-ee0b0244030434cdda26777bfb98962447e080cd.tar.xz
md/raid1,raid10: fix deadlock with freeze_array()
When raid1/raid10 needs to fix a read error, it first drains all pending requests by calling freeze_array(). This calls flush_pending_writes() if it needs to sleep, but some writes may be pending in a per-process plug rather than in the per-array request queue. When raid1{,0}_unplug() moves the request from the per-process plug to the per-array request queue (from which flush_pending_writes() can flush them), it needs to wake up freeze_array(), or freeze_array() will never flush them and so it will block forever. So add the requires wake_up() calls. This bug was introduced by commit f54a9d0e59c4bea3db733921ca9147612a6f292c for raid1 and a similar commit for RAID10, and so has been present since linux-3.6. As the bug causes a deadlock I believe this fix is suitable for -stable. Cc: stable@vger.kernel.org (3.6.y 3.7.y 3.8.y) Reported-by: Tregaron Bayly <tbayly@bluehost.com> Tested-by: Tregaron Bayly <tbayly@bluehost.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/Kconfig')
0 files changed, 0 insertions, 0 deletions