diff options
| author | NeilBrown <neilb@suse.de> | 2012-09-19 12:52:30 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-02 10:29:55 -0700 |
| commit | 9fd0132a29b4e40e5cf5ff82a02227b7f603bba7 (patch) | |
| tree | 8116196b1b2b4ec092a71a7a6f4feb59444ca028 /crypto/hmac.c | |
| parent | d765682ea82fb83fd8d01b7663f78b5d2f9fd839 (diff) | |
| download | linux-3.10-9fd0132a29b4e40e5cf5ff82a02227b7f603bba7.tar.gz linux-3.10-9fd0132a29b4e40e5cf5ff82a02227b7f603bba7.tar.bz2 linux-3.10-9fd0132a29b4e40e5cf5ff82a02227b7f603bba7.zip | |
md/raid5: fix calculate of 'degraded' when a replacement becomes active.
commit e5c86471f933608db5d43679f84cb4346c32033e upstream.
When a replacement device becomes active, we mark the device that it
replaces as 'faulty' so that it can subsequently get removed.
However 'calc_degraded' only pays attention to the primary device, not
the replacement, so the array appears to become degraded, which is
wrong.
So teach 'calc_degraded' to consider any replacement if a primary
device is faulty.
This is suitable for -stable as an incorrect 'degraded' value can
confuse md and could lead to data corruption.
This is only relevant for 3.3 and later.
Reported-by: Robin Hill <robin@robinhill.me.uk>
Reported-by: John Drescher <drescherjm@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/hmac.c')
0 files changed, 0 insertions, 0 deletions