ext4: use ext4_write_inode() when fsyncing w/o a journal
[linux-block.git] / fs / ext4 / fsync.c
CommitLineData
b2441318 1// SPDX-License-Identifier: GPL-2.0
ac27a0ec 2/*
617ba13b 3 * linux/fs/ext4/fsync.c
ac27a0ec
DK
4 *
5 * Copyright (C) 1993 Stephen Tweedie (sct@redhat.com)
6 * from
7 * Copyright (C) 1992 Remy Card (card@masi.ibp.fr)
8 * Laboratoire MASI - Institut Blaise Pascal
9 * Universite Pierre et Marie Curie (Paris VI)
10 * from
11 * linux/fs/minix/truncate.c Copyright (C) 1991, 1992 Linus Torvalds
12 *
617ba13b 13 * ext4fs fsync primitive
ac27a0ec
DK
14 *
15 * Big-endian to little-endian byte-swapping/bitmaps by
16 * David S. Miller (davem@caip.rutgers.edu), 1995
17 *
18 * Removed unnecessary code duplication for little endian machines
19 * and excessive __inline__s.
20 * Andi Kleen, 1997
21 *
22 * Major simplications and cleanup - we only need to do the metadata, because
23 * we can depend on generic_block_fdatasync() to sync the data blocks.
24 */
25
26#include <linux/time.h>
27#include <linux/fs.h>
28#include <linux/sched.h>
29#include <linux/writeback.h>
d755fb38 30#include <linux/blkdev.h>
9bffad1e 31
3dcf5451
CH
32#include "ext4.h"
33#include "ext4_jbd2.h"
ac27a0ec 34
9bffad1e
TT
35#include <trace/events/ext4.h>
36
14ece102
FM
37/*
38 * If we're not journaling and this is a just-created file, we have to
39 * sync our parent directory (if it was freshly created) since
40 * otherwise it will only be written by writeback, leaving a huge
41 * window during which a crash may lose the file. This may apply for
42 * the parent directory's parent as well, and so on recursively, if
43 * they are also freshly created.
44 */
0893ed45 45static int ext4_sync_parent(struct inode *inode)
14ece102
FM
46{
47 struct dentry *dentry = NULL;
d59729f4 48 struct inode *next;
0893ed45 49 int ret = 0;
14ece102 50
d59729f4
TT
51 if (!ext4_test_inode_state(inode, EXT4_STATE_NEWENTRY))
52 return 0;
53 inode = igrab(inode);
54 while (ext4_test_inode_state(inode, EXT4_STATE_NEWENTRY)) {
14ece102 55 ext4_clear_inode_state(inode, EXT4_STATE_NEWENTRY);
9f713878 56 dentry = d_find_any_alias(inode);
d59729f4 57 if (!dentry)
14ece102 58 break;
2b0143b5 59 next = igrab(d_inode(dentry->d_parent));
d59729f4
TT
60 dput(dentry);
61 if (!next)
62 break;
63 iput(inode);
64 inode = next;
6ae4c5a6
JK
65 /*
66 * The directory inode may have gone through rmdir by now. But
67 * the inode itself and its blocks are still allocated (we hold
68 * a reference to the inode so it didn't go through
69 * ext4_evict_inode()) and so we are safe to flush metadata
70 * blocks and the inode.
71 */
0893ed45
CW
72 ret = sync_mapping_buffers(inode->i_mapping);
73 if (ret)
74 break;
64744e03 75 ret = sync_inode_metadata(inode, 1);
0893ed45
CW
76 if (ret)
77 break;
14ece102 78 }
d59729f4 79 iput(inode);
0893ed45 80 return ret;
14ece102
FM
81}
82
ac27a0ec 83/*
617ba13b 84 * akpm: A new design for ext4_sync_file().
ac27a0ec
DK
85 *
86 * This is only called from sys_fsync(), sys_fdatasync() and sys_msync().
87 * There cannot be a transaction open by this task.
88 * Another task could have dirtied this inode. Its data can be in any
89 * state in the journalling system.
90 *
91 * What we do is just kick off a commit and wait on it. This will snapshot the
92 * inode to disk.
93 */
94
02c24a82 95int ext4_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
ac27a0ec 96{
7ea80859 97 struct inode *inode = file->f_mapping->host;
b436b9be 98 struct ext4_inode_info *ei = EXT4_I(inode);
d755fb38 99 journal_t *journal = EXT4_SB(inode->i_sb)->s_journal;
37b10dd0 100 int ret = 0, err;
b436b9be 101 tid_t commit_tid;
93628ffb 102 bool needs_barrier = false;
ac27a0ec 103
0db1ff22
TT
104 if (unlikely(ext4_forced_shutdown(EXT4_SB(inode->i_sb))))
105 return -EIO;
106
ac39849d 107 J_ASSERT(ext4_journal_current_handle() == NULL);
ac27a0ec 108
0562e0ba 109 trace_ext4_sync_file_enter(file, datasync);
ede86cc4 110
bc98a42c 111 if (sb_rdonly(inode->i_sb)) {
4418e141
DM
112 /* Make sure that we read updated s_mount_flags value */
113 smp_rmb();
114 if (EXT4_SB(inode->i_sb)->s_mount_flags & EXT4_MF_FS_ABORTED)
115 ret = -EROFS;
92e6222d 116 goto out;
4418e141 117 }
b436b9be 118
ad211f3e
TT
119 ret = file_write_and_wait_range(file, start, end);
120 if (ret)
121 return ret;
122
14ece102 123 if (!journal) {
ad211f3e
TT
124 struct writeback_control wbc = {
125 .sync_mode = WB_SYNC_ALL
126 };
127
128 ret = ext4_write_inode(inode, &wbc);
6ae4c5a6 129 if (!ret)
0893ed45 130 ret = ext4_sync_parent(inode);
78d96251
TT
131 if (test_opt(inode->i_sb, BARRIER))
132 goto issue_flush;
92e6222d 133 goto out;
14ece102 134 }
b436b9be 135
ac27a0ec 136 /*
b436b9be 137 * data=writeback,ordered:
ac27a0ec 138 * The caller's filemap_fdatawrite()/wait will sync the data.
b436b9be
JK
139 * Metadata is in the journal, we wait for proper transaction to
140 * commit here.
ac27a0ec
DK
141 *
142 * data=journal:
143 * filemap_fdatawrite won't do anything (the buffers are clean).
617ba13b 144 * ext4_force_commit will write the file data into the journal and
ac27a0ec
DK
145 * will wait on that.
146 * filemap_fdatawait() will encounter a ton of newly-dirtied pages
147 * (they were dirtied by commit). But that's OK - the blocks are
148 * safe in-journal, which is all fsync() needs to ensure.
149 */
0562e0ba
JZ
150 if (ext4_should_journal_data(inode)) {
151 ret = ext4_force_commit(inode->i_sb);
152 goto out;
153 }
ac27a0ec 154
b436b9be 155 commit_tid = datasync ? ei->i_datasync_tid : ei->i_sync_tid;
93628ffb
JK
156 if (journal->j_flags & JBD2_BARRIER &&
157 !jbd2_trans_will_send_data_barrier(journal, commit_tid))
158 needs_barrier = true;
d76a3a77 159 ret = jbd2_complete_transaction(journal, commit_tid);
a4a39040 160 if (needs_barrier) {
78d96251 161 issue_flush:
a4a39040
TT
162 err = blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, NULL);
163 if (!ret)
164 ret = err;
165 }
37b10dd0 166out:
0562e0ba 167 trace_ext4_sync_file_exit(inode, ret);
ac27a0ec
DK
168 return ret;
169}