diff options
| author | NeilBrown <neilb@suse.de> | 2012-11-22 08:12:09 +0400 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-11-22 08:12:42 +0400 |
| commit | 884162df2aadd7414bef4935e1a54976fd4e3988 (patch) | |
| tree | e562edba9a947346b124e9583de9d20f41c7f8c5 /drivers | |
| parent | e7c0c3fa29280d62aa5e11101a674bb3064bd791 (diff) | |
| download | linux-884162df2aadd7414bef4935e1a54976fd4e3988.tar.xz | |
md/raid10: decrement correct pending counter when writing to replacement.
When a write to a replacement device completes, we carefully
and correctly found the rdev that the write actually went to
and the blithely called rdev_dec_pending on the primary rdev,
even if this write was to the replacement.
This means that any writes to an array while a replacement
was ongoing would cause the nr_pending count for the primary
device to go negative, so it could never be removed.
This bug has been present since replacement was introduced in
3.3, so it is suitable for any -stable kernel since then.
Reported-by: "George Spelvin" <linux@horizon.com>
Cc: stable@vger.kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/md/raid10.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index ad032518fdc0..0d5d0ff2c0f7 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -499,7 +499,7 @@ static void raid10_end_write_request(struct bio *bio, int error) */ one_write_done(r10_bio); if (dec_rdev) - rdev_dec_pending(conf->mirrors[dev].rdev, conf->mddev); + rdev_dec_pending(rdev, conf->mddev); } /* |