kernel/git/stable/linux.git/fs/ext4/fsync.c, branch linux-2.6.31.y

ext4: Wait for proper transaction commit on fsync

2009-12-14T16:08:00+00:00

(cherry picked from commit b436b9bef84de6893e86346d8fbf7104bc520645) We cannot rely on buffer dirty bits during fsync because pdflush can come before fsync is called and clear dirty bits without forcing a transaction commit. What we do is that we track which transaction has last changed the inode and which transaction last changed allocation and force it to disk on fsync. Signed-off-by: Jan Kara Signed-off-by: "Theodore Ts'o" Signed-off-by: Greg Kroah-Hartman

ext4: avoid issuing unnecessary barriers

2009-12-14T16:07:39+00:00

(cherry picked from commit 6b17d902fdd241adfa4ce780df20547b28bf5801) We don't to issue an I/O barrier on an error or if we force commit because we are doing data journaling. Signed-off-by: "Theodore Ts'o" Cc: Jan Kara Signed-off-by: Greg Kroah-Hartman

ext4: async direct IO for holes and fallocate support

2009-12-14T16:07:03+00:00

(cherry picked from commit 8d5d02e6b176565c77ff03604908b1453a22044d) For async direct IO that covers holes or fallocate, the end_io callback function now queued the convertion work on workqueue but don't flush the work rightaway as it might take too long to afford. But when fsync is called after all the data is completed, user expects the metadata also being updated before fsync returns. Thus we need to flush the conversion work when fsync() is called. This patch keep track of a listed of completed async direct io that has a work queued on workqueue. When fsync() is called, it will go through the list and do the conversion. Signed-off-by: Mingming Cao Signed-off-by: Greg Kroah-Hartman

ext4: Assure that metadata blocks are written during fsync in no journal mode

2009-12-14T16:06:31+00:00

(cherry picked from commit fe188c0e084bdf3038dc0ac963c21d764f53f7da) When there is no journal present, we must attach buffer heads associated with extent tree and indirect blocks to the inode's mapping->private_list via mark_buffer_dirty_inode() so that ext4_sync_file() --- which is called to service fsync() and fdatasync() system calls --- can write out the inode's metadata blocks by calling sync_mapping_buffers(). Signed-off-by: "Theodore Ts'o" Signed-off-by: Greg Kroah-Hartman

ext4: fix cache flush in ext4_sync_file

2009-12-14T16:06:20+00:00

(cherry picked from commit 5f3481e9a80c240f169b36ea886e2325b9aeb745) We need to flush the write cache unconditionally in ->fsync, otherwise writes into already allocated blocks can get lost. Writes into fully allocated files are very common when using disk images for virtualization, and without this fix can easily lose data after an fdatasync, which is the typical implementation for a cache flush on the virtual drive. Signed-off-by: Christoph Hellwig Acked-by: Eric Sandeen Signed-off-by: "Theodore Ts'o"

ext4: convert instrumentation from markers to tracepoints

2009-06-17T15:48:11+00:00

Signed-off-by: "Theodore Ts'o"

ext4: Add debugging markers that can be used by systemtap

2008-10-06T00:50:06+00:00

This debugging markers are designed to debug problems such as the random filesystem latency problems reported by Arjan. Signed-off-by: "Theodore Ts'o"

ext4: Fix whitespace checkpatch warnings/errors

2008-09-09T02:25:24+00:00

Signed-off-by: "Theodore Ts'o"

ext4: call blkdev_issue_flush on fsync

2008-07-11T23:27:31+00:00

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 Signed-off-by: Mingming Cao Signed-off-by: "Theodore Ts'o"

ext4: move headers out of include/linux

2008-04-29T22:13:32+00:00

Move ext4 headers out of include/linux. This is just the trivial move, there's some more thing that could be done later. Signed-off-by: Christoph Hellwig Signed-off-by: Mingming Cao Signed-off-by: "Theodore Ts'o"