diff options
| author |   Eric Sandeen <sandeen@redhat.com> | 2008-07-11 19:27:31 -0400 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2008-07-11 19:27:31 -0400 |
| commit | d755fb384250d6bd7fd18a0930e71965acc8e72e (patch) | |
| tree | 7913bce90918cd26c8a5fe05f6c8943828e333bb /fs/jbd2/commit.c | |
| parent | ext4: cleanup block allocator (diff) | |
| download | wireguard-linux-d755fb384250d6bd7fd18a0930e71965acc8e72e.tar.xz wireguard-linux-d755fb384250d6bd7fd18a0930e71965acc8e72e.zip | |
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>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions