Hi,
as an update, I've been able to reproduce this bug reliably by using a
lot of RAM in order to force swap (I have vm_swappiness at 10).
Once swapping takes place, it's only a matter of time until some
userspace application locks at f2fs_issue_flush.
It will remain locked even when I free
allocate_segment_by_default is the only caller of change_curseg passing
@reuse with 'false', but commit 763bfe1bc575 ("f2fs: remove reusing any
prefree segments") removes the calling, after that, @reuse in
change_curseg always be true, so, let's clean up the unneeded parameter.
Signed-off-by:
f2fs enables hash-indexed directory by default, so we need to tag
FS_INDEX_FL in inode::i_flags during directory creataion, in order
to show correct status of inode in lsattr:
Before:
--- /mnt/f2fs/dir/
After:
---I--- /mnt/f2fs/dir/
Signed-off-by: Chao Yu
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Linux-f2fs-devel mailing list
