]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
projects / linux-2.6-omap-h63xx.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 654b490) | patch
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)
commitd755fb384250d6bd7fd18a0930e71965acc8e72e
tree7913bce90918cd26c8a5fe05f6c8943828e333bbtree | snapshot
parent654b4908bc17a6318d18f3036fecc5155de92f55commit | 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>
fs/ext4/fsync.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.