diff options
| author | Harshad Shirwadkar <harshadshirwadkar@gmail.com> | 2021-10-15 20:25:13 +0200 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2021-11-04 15:34:39 +0100 |
| commit | 1ebf21784b19d5bc269f39a5d1eedb7f29a7d152 (patch) | |
| tree | e40e09433596daca12c0d13632d584fc55b31b7e /fs/ext4/extents.c | |
| parent | ext4: commit inline data during fast commit (diff) | |
| download | linux-1ebf21784b19d5bc269f39a5d1eedb7f29a7d152.tar.xz linux-1ebf21784b19d5bc269f39a5d1eedb7f29a7d152.zip | |
ext4: inline data inode fast commit replay fixes
Since there are no blocks in an inline data inode, there's no point in
fixing iblocks field in fast commit replay path for this inode.
Similarly, there's no point in fixing any block bitmaps / global block
counters with respect to such an inode. Just bail out from these
functions if an inline data inode is encountered.
Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Link: https://lore.kernel.org/r/20211015182513.395917-2-harshads@google.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/extents.c')
| -rw-r--r-- | fs/ext4/extents.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index 09f56e04f4b2..0ecf819bf189 100644 --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -6071,6 +6071,9 @@ int ext4_ext_clear_bb(struct inode *inode) int j, ret = 0; struct ext4_map_blocks map; + if (ext4_test_inode_flag(inode, EXT4_INODE_INLINE_DATA)) + return 0; + /* Determin the size of the file first */ path = ext4_find_extent(inode, EXT_MAX_BLOCKS - 1, NULL, EXT4_EX_NOCACHE); |