diff options
| author | Shaohua Li <shli@fb.com> | 2015-09-18 19:20:12 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.com> | 2015-10-02 09:23:44 +0200 |
| commit | d4929add83ad4660b1824a9282ab5dd4d60140fa (patch) | |
| tree | c087245ba01366fb5c568915fce7d353897cc7a1 /crypto/rmd256.c | |
| parent | md/raid0: apply base queue limits *before* disk_stack_limits (diff) | |
| download | linux-d4929add83ad4660b1824a9282ab5dd4d60140fa.tar.xz linux-d4929add83ad4660b1824a9282ab5dd4d60140fa.zip | |
md: clear CHANGE_PENDING in readonly array
If faulty disks of an array are more than allowed degraded number, the
array enters error handling. It will be marked as read-only with
MD_CHANGE_PENDING/RECOVERY_NEEDED set. But currently recovery doesn't
clear CHANGE_PENDING bit for read-only array. If MD_CHANGE_PENDING is
set for a raid5 array, all returned IO will be hold on a list till the
bit is clear. But recovery nevery clears this bit, the IO is always in
pending state and nevery finish. This has bad effects like upper layer
can't get an IO error and the array can't be stopped.
Fixes: c3cce6cda162 ("md/raid5: ensure device failure recorded before write request returns.")
Signed-off-by: Shaohua Li <shli@fb.com>
Signed-off-by: NeilBrown <neilb@suse.com>
Diffstat (limited to 'crypto/rmd256.c')
0 files changed, 0 insertions, 0 deletions