]> git.baikalelectronics.ru Git - kernel.git/commit
ext4: call blkdev_issue_flush on fsync
authorEric Sandeen <sandeen@redhat.com>
Fri, 11 Jul 2008 23:27:31 +0000 (19:27 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 11 Jul 2008 23:27:31 +0000 (19:27 -0400)
commita6678d492756f91dd621c8d235ac0fed65ff7733
tree7913bce90918cd26c8a5fe05f6c8943828e333bb
parent79d2cc47cd43d9e43bef1ad2b27640ae8df519d5
ext4: call blkdev_issue_flush on fsync

To ensure that bits are truly on-disk after an fsync,
we should call blkdev_issue_flush if barriers are supported.

Inspired by an old thread on barriers, by reiserfs & xfs
which do the same, and by a patch SuSE ships with their kernel

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/ext4/fsync.c