diff options
| author | NeilBrown <neilb@suse.com> | 2015-07-24 05:27:08 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.com> | 2015-08-31 19:38:17 +0200 |
| commit | 5ed1df2eacc0ba92c8c7e2499c97594b5ef928a8 (patch) | |
| tree | d712ddbdc3bfcbc710f6823076691e96f197baf7 /drivers/input/ff-memless.c | |
| parent | md: be careful when testing resync_max against curr_resync_completed. (diff) | |
| download | linux-5ed1df2eacc0ba92c8c7e2499c97594b5ef928a8.tar.xz linux-5ed1df2eacc0ba92c8c7e2499c97594b5ef928a8.zip | |
md: sync sync_completed has correct value as recovery finishes.
There can be a small window between the moment that recovery
actually writes the last block and the time when various sysfs
and /proc/mdstat attributes report that it has finished.
During this time, 'sync_completed' can have the wrong value.
This can confuse monitoring software.
So:
- don't set curr_resync_completed beyond the end of the devices,
- set it correctly when resync/recovery has completed.
Signed-off-by: NeilBrown <neilb@suse.com>
Diffstat (limited to 'drivers/input/ff-memless.c')
0 files changed, 0 insertions, 0 deletions