diff options
| author | Nigel Croxon <[email protected]> | 2019-04-16 09:50:09 -0700 |
|---|---|---|
| committer | Song Liu <[email protected]> | 2019-04-16 14:33:18 -0700 |
| commit | b2176a1dfb518d870ee073445d27055fea64dfb8 (patch) | |
| tree | 0d95541e3b7f29186b6a837a7746a294c59f62bb /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py | |
| parent | a25d8c327bb41742dbd59f8c545f59f3b9c39983 (diff) | |
md/raid: raid5 preserve the writeback action after the parity check
The problem is that any 'uptodate' vs 'disks' check is not precise
in this path. Put a "WARN_ON(!test_bit(R5_UPTODATE, &dev->flags)" on the
device that might try to kick off writes and then skip the action.
Better to prevent the raid driver from taking unexpected action *and* keep
the system alive vs killing the machine with BUG_ON.
Note: fixed warning reported by kbuild test robot <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Signed-off-by: Nigel Croxon <[email protected]>
Signed-off-by: Song Liu <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py')
0 files changed, 0 insertions, 0 deletions