md/raid5: In ops_run_io, inc nr_pending before calling md_wait_for_blocked_rdev
authormajianpeng <majianpeng@gmail.com>
Tue, 3 Jul 2012 02:11:54 +0000 (12:11 +1000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 16 Jul 2012 16:04:25 +0000 (09:04 -0700)
commit8d9369807370331cebf3e237b95ecce068af80f1
tree45d0c283ffd7f058e28a17d6b55e0a8a3d567502
parent65c3f18b9032f7237fc74403ce3a92176eaebd8c
md/raid5: In ops_run_io, inc nr_pending before calling md_wait_for_blocked_rdev

commit 1850753d2e6d9ca7856581ca5d3cf09521e6a5d7 upstream.

In ops_run_io(), the call to md_wait_for_blocked_rdev will decrement
nr_pending so we lose the reference we hold on the rdev.
So atomic_inc it first to maintain the reference.

This bug was introduced by commit  73e92e51b7969ef5477d
    md/raid5.  Don't write to known bad block on doubtful devices.

which appeared in 3.0, so patch is suitable for stable kernels since
then.

Signed-off-by: majianpeng <majianpeng@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/md/raid5.c