diff options
| author |  Roman Pen <r.peniaev@gmail.com>
| 2015-09-15 08:27:25 -0600 |
|---|---|---|
| committer |  Jens Axboe <axboe@fb.com>
| 2015-09-23 11:00:57 -0600 |
| commit | 5948edbcbf43759586cdf2656d293ea7de310280 (patch) | |
| tree | 50f982a917ed1884e5402a448ae2a9846ee0fac2 /fs/direct-io.c | |
| parent | block: kmemleak: Track the page allocations for struct request (diff) | |
| download | linux-5948edbcbf43759586cdf2656d293ea7de310280.tar.gz linux-5948edbcbf43759586cdf2656d293ea7de310280.tar.bz2 linux-5948edbcbf43759586cdf2656d293ea7de310280.zip | |
fs/mpage.c: forgotten WRITE_SYNC in case of data integrity write
In case of wbc->sync_mode == WB_SYNC_ALL we need to do data integrity
write, thus mark request as WRITE_SYNC.
akpm: afaict this change will cause the data integrity write bios to be
placed onto the second queue in cfq_io_cq.cfqq[], which presumably results
in special treatment. The documentation for REQ_SYNC is horrid.
Signed-off-by: Roman Pen <r.peniaev@gmail.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions