summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-10-26 10:31:04 +1100
committerGreg Kroah-Hartman <gregkh@suse.de>2011-11-11 09:35:53 -0800
commita847627709b3402163d99f7c6fda4a77bcd6b51b (patch)
treee89e09e41858afe7f317fa7ef467180ec4a46db9 /tools
parente747500485ddef175ac6694dcff4fd8088e62071 (diff)
md/raid5: fix bug that could result in reads from a failed device.
commit 355840e7a7e56bb2834fd3b0da64da5465f8aeaa upstream. This bug was introduced in 415e72d034c50520ddb7ff79e7d1792c1306f0c9 which was in 2.6.36. There is a small window of time between when a device fails and when it is removed from the array. During this time we might still read from it, but we won't write to it - so it is possible that we could read stale data. We didn't need the test of 'Faulty' before because the test on In_sync is sufficient. Since we started allowing reads from the early part of non-In_sync devices we need a test on Faulty too. This is suitable for any kernel from 2.6.36 onwards, though the patch might need a bit of tweaking in 3.0 and earlier. Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions