Daniel Verkamp ca39ac0a95 devices: block: issue fsync when FlushTimer expires ... The RequestType::Flush handler correctly uses fsync(), which issues an fsync to the underlying disk image file. However, the flush timer (started on write and cancelled if a flush request is executed) was only calling flush(), which is insufficient when the disk image is a raw file - it just flushes in-memory buffers and does not issue an fsync. BUG=None TEST=Issue writes in crosvm; verify fsync in strace output Change-Id: I1de8a35615031b5fdf5599dd6b49015d0b245c31 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1632876 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>		2019-05-29 06:27:33 -07:00
..
src	devices: block: issue fsync when FlushTimer expires	2019-05-29 06:27:33 -07:00
Cargo.toml	edition: Update devices crate to 2018 edition	2019-04-15 02:06:04 -07:00