diff options
| author | Namhyung Kim <[email protected]> | 2011-06-14 14:20:19 +1000 |
|---|---|---|
| committer | NeilBrown <[email protected]> | 2011-06-14 14:20:19 +1000 |
| commit | b062962edb086011e94ec4d9eb3f6a6d814f2a8f (patch) | |
| tree | 4b832dab3687db5b719266d758a916bbc118e1f0 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 9b2dc8b665932a8e681a7ab3237f60475e75e161 (diff) | |
md/raid5: fix FUA request handling in ops_run_io()
Commit e9c7469bb4f5 ("md: implment REQ_FLUSH/FUA support")
introduced R5_WantFUA flag and set rw to WRITE_FUA in that case.
However remaining code still checks whether rw is exactly same
as WRITE or not, so FUAed-write ends up with being treated as
READ. Fix it.
This bug has been present since 2.6.37 and the fix is suitable for any
-stable kernel since then. It is not clear why this has not caused
more problems.
Cc: Tejun Heo <[email protected]>
Cc: [email protected]
Signed-off-by: Namhyung Kim <[email protected]>
Signed-off-by: NeilBrown <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions