| commit | d755fb384250d6bd7fd18a0930e71965acc8e72e | [log] [tgz] |
|---|---|---|
| author | Eric Sandeen <sandeen@redhat.com> | Fri Jul 11 19:27:31 2008 -0400 |
| committer | Theodore Ts'o <tytso@mit.edu> | Fri Jul 11 19:27:31 2008 -0400 |
| tree | 7913bce90918cd26c8a5fe05f6c8943828e333bb | |
| parent | 654b4908bc17a6318d18f3036fecc5155de92f55 [diff] |
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>