linux-toradex.git/fs/f2fs/inode.c, branch v4.10

f2fs: record inode updating status correctly

2016-11-23T20:11:25+00:00

We should record updating status of inode only for living inode, for those
unlinked inode it needs to clear its ino cache, otherwise after the ino
was been reused, it will cause unneeded node page writing during ->fsync.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: make clean inodes when flushing inode page

2016-11-23T20:11:09+00:00

This patch tries to make more clean inodes when flushing dirty inodes in
checkpoint.

Signed-off-by: Jaegeuk Kim

f2fs: keep dirty inodes selectively for checkpoint

2016-11-23T20:11:08+00:00

This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.

The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount

In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: clear nlink if fail to add_link

2016-11-23T20:10:59+00:00

We don't need to keep incomplete created inode in cache, so if we fail to
add link into directory during new inode creation, it's better to set
nlink of inode to zero, then we can evict inode immediately. Otherwise
release of nid belong to inode will be delayed until inode cache is being
shrunk, it may cause a seemingly endless loop while allocating free nids
in time of testing generic/269 case of fstest suit.

Signed-off-by: Chao Yu 
[Jaegeuk Kim: add update_inode_page to fix kernel panic]
Signed-off-by: Jaegeuk Kim

f2fs: fix to update largest extent under lock

2016-11-23T20:10:55+00:00

In order to avoid racing problem, make largest extent cache being updated
under lock.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: support configuring fault injection per superblock

2016-10-01T00:34:31+00:00

Previously, we only support global fault injection configuration, so that
when we configure type/rate of fault injection through sysfs, mount
option, it will influence all f2fs partition which is being used.

It is not make sence, since it will be not convenient if developer want
to test separated partitions with different fault injection rate/type
simultaneously, also it's not possible to enable fault injection in one
partition and disable fault injection in other one.

>From now on, we move global configuration of fault injection in module
into per-superblock, hence injection testing can be more flexible.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: avoid ENOMEM during roll-forward recovery

2016-09-13T20:02:29+00:00

This patch gives another chances during roll-forward recovery regarding to
-ENOMEM.

Signed-off-by: Jaegeuk Kim

f2fs: avoid mark_inode_dirty

2016-07-08T17:34:09+00:00

Let's check inode's dirtiness before calling mark_inode_dirty.

Signed-off-by: Jaegeuk Kim

f2fs: call update_inode_page for orphan inodes

2016-07-06T17:44:07+00:00

Let's store orphan inode pages right away.

Signed-off-by: Jaegeuk Kim

f2fs: avoid data race between FI_DIRTY_INODE flag and update_inode

2016-06-07T16:45:40+00:00

FI_DIRTY_INODE flag is not covered by inode page lock, so it can be unset
at any time like below.

Thread #1                        Thread #2
- lock_page(ipage)
- update i_fields
                                 - update i_size/i_blocks/and so on
				 - set FI_DIRTY_INODE
- reset FI_DIRTY_INODE
- set_page_dirty(ipage)

In this case, we can lose the latest i_field information.

Signed-off-by: Jaegeuk Kim