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
..
pci	devices: Add capture path in AC'97 PCI device	2019-04-20 03:58:47 -07:00
register_space
usb	crosvm: update xhci abi to use new bit_field features	2019-05-25 02:31:16 -07:00
utils	usb: set event loop thread name	2019-05-08 19:35:15 -07:00
virtio	devices: block: issue fsync when FlushTimer expires	2019-05-29 06:27:33 -07:00
bus.rs
cmos.rs	devices: cmos: report memory size in CMOS	2019-05-23 02:14:28 -07:00
i8042.rs
ioapic.rs
lib.rs	crosvm: add cmdline flags for configuring serial outputs in guest machine	2019-05-15 13:36:25 -07:00
pic.rs
pit.rs
pl030.rs
proxy.rs
serial.rs	devices: serial: implement MSR loop behavior	2019-05-23 02:14:11 -07:00
split_irqchip_common.rs