summaryrefslogtreecommitdiff
path: root/fs/ext4/ext4.h
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2008-07-12 03:27:31 +0400
committerTheodore Ts'o <tytso@mit.edu>2008-07-12 03:27:31 +0400
commitd755fb384250d6bd7fd18a0930e71965acc8e72e (patch)
tree7913bce90918cd26c8a5fe05f6c8943828e333bb /fs/ext4/ext4.h
parent654b4908bc17a6318d18f3036fecc5155de92f55 (diff)
downloadlinux-d755fb384250d6bd7fd18a0930e71965acc8e72e.tar.xz
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/ext4/ext4.h')
0 files changed, 0 insertions, 0 deletions