2006-10-11 01:20:50 -07:00
|
|
|
/*
|
2006-10-11 01:20:53 -07:00
|
|
|
* linux/fs/ext4/fsync.c
|
2006-10-11 01:20:50 -07:00
|
|
|
*
|
|
|
|
* Copyright (C) 1993 Stephen Tweedie (sct@redhat.com)
|
|
|
|
* from
|
|
|
|
* Copyright (C) 1992 Remy Card (card@masi.ibp.fr)
|
|
|
|
* Laboratoire MASI - Institut Blaise Pascal
|
|
|
|
* Universite Pierre et Marie Curie (Paris VI)
|
|
|
|
* from
|
|
|
|
* linux/fs/minix/truncate.c Copyright (C) 1991, 1992 Linus Torvalds
|
|
|
|
*
|
2006-10-11 01:20:53 -07:00
|
|
|
* ext4fs fsync primitive
|
2006-10-11 01:20:50 -07:00
|
|
|
*
|
|
|
|
* Big-endian to little-endian byte-swapping/bitmaps by
|
|
|
|
* David S. Miller (davem@caip.rutgers.edu), 1995
|
|
|
|
*
|
|
|
|
* Removed unnecessary code duplication for little endian machines
|
|
|
|
* and excessive __inline__s.
|
|
|
|
* Andi Kleen, 1997
|
|
|
|
*
|
|
|
|
* Major simplications and cleanup - we only need to do the metadata, because
|
|
|
|
* we can depend on generic_block_fdatasync() to sync the data blocks.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/time.h>
|
|
|
|
#include <linux/fs.h>
|
|
|
|
#include <linux/sched.h>
|
|
|
|
#include <linux/writeback.h>
|
2006-10-11 01:21:01 -07:00
|
|
|
#include <linux/jbd2.h>
|
2008-07-11 16:27:31 -07:00
|
|
|
#include <linux/blkdev.h>
|
2009-06-17 08:48:11 -07:00
|
|
|
|
2008-04-29 15:13:32 -07:00
|
|
|
#include "ext4.h"
|
|
|
|
#include "ext4_jbd2.h"
|
2006-10-11 01:20:50 -07:00
|
|
|
|
2009-06-17 08:48:11 -07:00
|
|
|
#include <trace/events/ext4.h>
|
|
|
|
|
2010-10-27 18:30:14 -07:00
|
|
|
static void dump_completed_IO(struct inode * inode)
|
|
|
|
{
|
|
|
|
#ifdef EXT4_DEBUG
|
|
|
|
struct list_head *cur, *before, *after;
|
|
|
|
ext4_io_end_t *io, *io0, *io1;
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
if (list_empty(&EXT4_I(inode)->i_completed_io_list)){
|
|
|
|
ext4_debug("inode %lu completed_io list is empty\n", inode->i_ino);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
ext4_debug("Dump inode %lu completed_io list \n", inode->i_ino);
|
|
|
|
spin_lock_irqsave(&EXT4_I(inode)->i_completed_io_lock, flags);
|
|
|
|
list_for_each_entry(io, &EXT4_I(inode)->i_completed_io_list, list){
|
|
|
|
cur = &io->list;
|
|
|
|
before = cur->prev;
|
|
|
|
io0 = container_of(before, ext4_io_end_t, list);
|
|
|
|
after = cur->next;
|
|
|
|
io1 = container_of(after, ext4_io_end_t, list);
|
|
|
|
|
|
|
|
ext4_debug("io 0x%p from inode %lu,prev 0x%p,next 0x%p\n",
|
|
|
|
io, inode->i_ino, io0, io1);
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&EXT4_I(inode)->i_completed_io_lock, flags);
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This function is called from ext4_sync_file().
|
|
|
|
*
|
|
|
|
* When IO is completed, the work to convert unwritten extents to
|
|
|
|
* written is queued on workqueue but may not get immediately
|
|
|
|
* scheduled. When fsync is called, we need to ensure the
|
|
|
|
* conversion is complete before fsync returns.
|
|
|
|
* The inode keeps track of a list of pending/completed IO that
|
|
|
|
* might needs to do the conversion. This function walks through
|
|
|
|
* the list and convert the related unwritten extents for completed IO
|
|
|
|
* to written.
|
|
|
|
* The function return the number of pending IOs on success.
|
|
|
|
*/
|
2011-01-10 10:47:05 -07:00
|
|
|
extern int ext4_flush_completed_IO(struct inode *inode)
|
2010-10-27 18:30:14 -07:00
|
|
|
{
|
|
|
|
ext4_io_end_t *io;
|
|
|
|
struct ext4_inode_info *ei = EXT4_I(inode);
|
|
|
|
unsigned long flags;
|
|
|
|
int ret = 0;
|
|
|
|
int ret2 = 0;
|
|
|
|
|
|
|
|
if (list_empty(&ei->i_completed_io_list))
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
dump_completed_IO(inode);
|
|
|
|
spin_lock_irqsave(&ei->i_completed_io_lock, flags);
|
|
|
|
while (!list_empty(&ei->i_completed_io_list)){
|
|
|
|
io = list_entry(ei->i_completed_io_list.next,
|
|
|
|
ext4_io_end_t, list);
|
|
|
|
/*
|
|
|
|
* Calling ext4_end_io_nolock() to convert completed
|
|
|
|
* IO to written.
|
|
|
|
*
|
|
|
|
* When ext4_sync_file() is called, run_queue() may already
|
|
|
|
* about to flush the work corresponding to this io structure.
|
|
|
|
* It will be upset if it founds the io structure related
|
|
|
|
* to the work-to-be schedule is freed.
|
|
|
|
*
|
|
|
|
* Thus we need to keep the io structure still valid here after
|
2011-03-30 18:57:33 -07:00
|
|
|
* conversion finished. The io structure has a flag to
|
2010-10-27 18:30:14 -07:00
|
|
|
* avoid double converting from both fsync and background work
|
|
|
|
* queue work.
|
|
|
|
*/
|
|
|
|
spin_unlock_irqrestore(&ei->i_completed_io_lock, flags);
|
|
|
|
ret = ext4_end_io_nolock(io);
|
|
|
|
spin_lock_irqsave(&ei->i_completed_io_lock, flags);
|
|
|
|
if (ret < 0)
|
|
|
|
ret2 = ret;
|
|
|
|
else
|
|
|
|
list_del_init(&io->list);
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&ei->i_completed_io_lock, flags);
|
|
|
|
return (ret2 < 0) ? ret2 : 0;
|
|
|
|
}
|
|
|
|
|
2010-05-17 05:00:00 -07:00
|
|
|
/*
|
|
|
|
* If we're not journaling and this is a just-created file, we have to
|
|
|
|
* sync our parent directory (if it was freshly created) since
|
|
|
|
* otherwise it will only be written by writeback, leaving a huge
|
|
|
|
* window during which a crash may lose the file. This may apply for
|
|
|
|
* the parent directory's parent as well, and so on recursively, if
|
|
|
|
* they are also freshly created.
|
|
|
|
*/
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
static int ext4_sync_parent(struct inode *inode)
|
2010-05-17 05:00:00 -07:00
|
|
|
{
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
struct writeback_control wbc;
|
2010-05-17 05:00:00 -07:00
|
|
|
struct dentry *dentry = NULL;
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
int ret = 0;
|
2010-05-17 05:00:00 -07:00
|
|
|
|
|
|
|
while (inode && ext4_test_inode_state(inode, EXT4_STATE_NEWENTRY)) {
|
|
|
|
ext4_clear_inode_state(inode, EXT4_STATE_NEWENTRY);
|
|
|
|
dentry = list_entry(inode->i_dentry.next,
|
|
|
|
struct dentry, d_alias);
|
|
|
|
if (!dentry || !dentry->d_parent || !dentry->d_parent->d_inode)
|
|
|
|
break;
|
|
|
|
inode = dentry->d_parent->d_inode;
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
ret = sync_mapping_buffers(inode->i_mapping);
|
|
|
|
if (ret)
|
|
|
|
break;
|
|
|
|
memset(&wbc, 0, sizeof(wbc));
|
|
|
|
wbc.sync_mode = WB_SYNC_ALL;
|
|
|
|
wbc.nr_to_write = 0; /* only write out the inode */
|
|
|
|
ret = sync_inode(inode, &wbc);
|
|
|
|
if (ret)
|
|
|
|
break;
|
2010-05-17 05:00:00 -07:00
|
|
|
}
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
return ret;
|
2010-05-17 05:00:00 -07:00
|
|
|
}
|
|
|
|
|
2006-10-11 01:20:50 -07:00
|
|
|
/*
|
2006-10-11 01:20:53 -07:00
|
|
|
* akpm: A new design for ext4_sync_file().
|
2006-10-11 01:20:50 -07:00
|
|
|
*
|
|
|
|
* This is only called from sys_fsync(), sys_fdatasync() and sys_msync().
|
|
|
|
* There cannot be a transaction open by this task.
|
|
|
|
* Another task could have dirtied this inode. Its data can be in any
|
|
|
|
* state in the journalling system.
|
|
|
|
*
|
|
|
|
* What we do is just kick off a commit and wait on it. This will snapshot the
|
|
|
|
* inode to disk.
|
2009-09-28 12:48:29 -07:00
|
|
|
*
|
|
|
|
* i_mutex lock is held when entering and exiting this function
|
2006-10-11 01:20:50 -07:00
|
|
|
*/
|
|
|
|
|
2010-05-26 08:53:25 -07:00
|
|
|
int ext4_sync_file(struct file *file, int datasync)
|
2006-10-11 01:20:50 -07:00
|
|
|
{
|
2010-05-26 08:53:25 -07:00
|
|
|
struct inode *inode = file->f_mapping->host;
|
2009-12-08 21:51:10 -07:00
|
|
|
struct ext4_inode_info *ei = EXT4_I(inode);
|
2008-07-11 16:27:31 -07:00
|
|
|
journal_t *journal = EXT4_SB(inode->i_sb)->s_journal;
|
2009-12-08 21:51:10 -07:00
|
|
|
int ret;
|
|
|
|
tid_t commit_tid;
|
2006-10-11 01:20:50 -07:00
|
|
|
|
2007-10-16 15:38:25 -07:00
|
|
|
J_ASSERT(ext4_journal_current_handle() == NULL);
|
2006-10-11 01:20:50 -07:00
|
|
|
|
2011-03-21 18:38:05 -07:00
|
|
|
trace_ext4_sync_file_enter(file, datasync);
|
2008-10-05 17:50:06 -07:00
|
|
|
|
2009-12-08 21:51:10 -07:00
|
|
|
if (inode->i_sb->s_flags & MS_RDONLY)
|
|
|
|
return 0;
|
|
|
|
|
2011-01-10 10:47:05 -07:00
|
|
|
ret = ext4_flush_completed_IO(inode);
|
2009-09-28 12:48:29 -07:00
|
|
|
if (ret < 0)
|
2011-03-21 18:38:05 -07:00
|
|
|
goto out;
|
2010-05-17 04:00:00 -07:00
|
|
|
|
2010-05-17 05:00:00 -07:00
|
|
|
if (!journal) {
|
2010-05-26 08:53:41 -07:00
|
|
|
ret = generic_file_fsync(file, datasync);
|
2010-05-17 05:00:00 -07:00
|
|
|
if (!ret && !list_empty(&inode->i_dentry))
|
ext4: sync the directory inode in ext4_sync_parent()
ext4 has taken the stance that, in the absence of a journal,
when an fsync/fdatasync of an inode is done, the parent
directory should be sync'ed if this inode entry is new.
ext4_sync_parent(), which implements this, does indeed sync
the dirent pages for parent directories, but it does not
sync the directory *inode*. This patch fixes this.
Also now return error status from ext4_sync_parent().
I tested this using a power fail test, which panics a
machine running a file server getting requests from a
client. Without this patch, on about every other test run,
the server is missing many, many files that had been synced.
With this patch, on > 6 runs, I see zero files being lost.
Google-Bug-Id: 4179519
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-04-10 19:05:31 -07:00
|
|
|
ret = ext4_sync_parent(inode);
|
2011-03-21 18:38:05 -07:00
|
|
|
goto out;
|
2010-05-17 05:00:00 -07:00
|
|
|
}
|
2009-12-08 21:51:10 -07:00
|
|
|
|
2006-10-11 01:20:50 -07:00
|
|
|
/*
|
2009-12-08 21:51:10 -07:00
|
|
|
* data=writeback,ordered:
|
2006-10-11 01:20:50 -07:00
|
|
|
* The caller's filemap_fdatawrite()/wait will sync the data.
|
2009-12-08 21:51:10 -07:00
|
|
|
* Metadata is in the journal, we wait for proper transaction to
|
|
|
|
* commit here.
|
2006-10-11 01:20:50 -07:00
|
|
|
*
|
|
|
|
* data=journal:
|
|
|
|
* filemap_fdatawrite won't do anything (the buffers are clean).
|
2006-10-11 01:20:53 -07:00
|
|
|
* ext4_force_commit will write the file data into the journal and
|
2006-10-11 01:20:50 -07:00
|
|
|
* will wait on that.
|
|
|
|
* filemap_fdatawait() will encounter a ton of newly-dirtied pages
|
|
|
|
* (they were dirtied by commit). But that's OK - the blocks are
|
|
|
|
* safe in-journal, which is all fsync() needs to ensure.
|
|
|
|
*/
|
2011-03-21 18:38:05 -07:00
|
|
|
if (ext4_should_journal_data(inode)) {
|
|
|
|
ret = ext4_force_commit(inode->i_sb);
|
|
|
|
goto out;
|
|
|
|
}
|
2006-10-11 01:20:50 -07:00
|
|
|
|
2009-12-08 21:51:10 -07:00
|
|
|
commit_tid = datasync ? ei->i_datasync_tid : ei->i_sync_tid;
|
2009-12-23 04:52:08 -07:00
|
|
|
if (jbd2_log_start_commit(journal, commit_tid)) {
|
|
|
|
/*
|
|
|
|
* When the journal is on a different device than the
|
|
|
|
* fs data disk, we need to issue the barrier in
|
|
|
|
* writeback mode. (In ordered mode, the jbd2 layer
|
|
|
|
* will take care of issuing the barrier. In
|
|
|
|
* data=journal, all of the data blocks are written to
|
|
|
|
* the journal device.)
|
|
|
|
*/
|
|
|
|
if (ext4_should_writeback_data(inode) &&
|
|
|
|
(journal->j_fs_dev != journal->j_dev) &&
|
|
|
|
(journal->j_flags & JBD2_BARRIER))
|
2010-04-28 06:55:06 -07:00
|
|
|
blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL,
|
2010-09-16 11:51:46 -07:00
|
|
|
NULL);
|
2010-05-09 21:00:00 -07:00
|
|
|
ret = jbd2_log_wait_commit(journal, commit_tid);
|
2009-12-23 04:52:08 -07:00
|
|
|
} else if (journal->j_flags & JBD2_BARRIER)
|
2010-09-16 11:51:46 -07:00
|
|
|
blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, NULL);
|
2011-03-21 18:38:05 -07:00
|
|
|
out:
|
|
|
|
trace_ext4_sync_file_exit(inode, ret);
|
2006-10-11 01:20:50 -07:00
|
|
|
return ret;
|
|
|
|
}
|