On 2024/8/20 14:58, Chao Yu wrote:
On 2024/8/20 12:38, Li Zetao wrote:
I want to apply your patch set for testing, but there is a conflict on
the master branch of linux-next. Maybe it depends on a certain pre-patch.
Please let me know, thank you.
Applying: f2fs: convert f2fs_write_begin()
On 2024/8/20 10:44, Sunmin Jeong wrote:
Hello Chao Yu,
SQLite App GC Thread Shrinker
- f2fs_ioc_start_atomic_write
- f2fs_ioc_commit_atomic_write
- f2fs_commit_atomic_write
- filemap_write_and_wait_range
: write atomic_file's data to cow_inode
On 2024/8/28 23:27, Jaegeuk Kim wrote:
On 08/14, Chao Yu wrote:
SQLite App GC Thread Shrinker
- f2fs_ioc_start_atomic_write
- f2fs_ioc_commit_atomic_write
- f2fs_commit_atomic_write
- filemap_write_and_wait_range
: write atomic_file's data to cow_inode
On 2024/8/27 14:22, wangzijie wrote:
Thread A
-dquot_initialize
-dqget
-f2fs_dquot_acquire
-v2_read_dquot
-qtree_read_dquot
-find_tree_dqentry
-f2fs_quota_read
-read_cache_page_gfp
-do_read_cache_folio
-fiemap_read_folio
-folio_wait
On 2024/8/29 0:54, Julian Sun wrote:
Hi, all.
Recently syzbot reported a bug as following:
kernel BUG at fs/f2fs/inode.c:896!
CPU: 1 UID: 0 PID: 5217 Comm: syz-executor605 Not tainted
6.11.0-rc4-syzkaller-00033-g872cf28b8df9 #0
RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896
Call
On 2024/8/27 4:23, Daeho Jeong wrote:
From: Daeho Jeong
Keep atomic file clean while updating and make it dirtied during commit
in order to avoid unnecessary and excessive inode updates in the previous
fix.
Fixes: 4bf78322346f ("f2fs: mark inode dirty for FI_ATOMIC_COMMITTED flag")
Signed-off-
The bug related to this regression testcase has been fixed by commit
b40a2b003709 ("f2fs: use meta inode for GC of atomic file"), let's
add missing _fixed_by_kernel_commit line for this testcase.
Cc: Jaegeuk Kim
Cc: Daeho Jeong
Signed-off-by: Chao Yu
---
tests/f2fs/003 | 3 +++
1 file changed,
On 2024/9/2 21:01, Julian Sun wrote:
On Mon, 2024-09-02 at 16:13 +0800, Chao Yu wrote:
On 2024/8/29 0:54, Julian Sun wrote:
Hi, all.
Recently syzbot reported a bug as following:
kernel BUG at fs/f2fs/inode.c:896!
CPU: 1 UID: 0 PID: 5217 Comm: syz-executor605 Not tainted
6.11.0-rc4-syzkaller-0
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
On 2024/8/22 23:38, syzbot wrote:
syzbot has found a reproducer for the following issue on:
HEAD commit:872cf28b8df9 Merge tag 'platform-drivers-x86-v6.11-4' of g..
git tree: upstream
console+strace: https://sy
On 2024/9/4 1:07, Daeho Jeong wrote:
On Mon, Sep 2, 2024 at 3:08 AM Chao Yu wrote:
On 2024/8/27 4:23, Daeho Jeong wrote:
From: Daeho Jeong
Keep atomic file clean while updating and make it dirtied during commit
in order to avoid unnecessary and excessive inode updates in the previous
fix.
If there are double '.' or '..' dirents in directory, fsck.f2fs won't
detect and repaire the issue correctly, fix it.
Reviewed-by: Sheng Yong
Signed-off-by: Chao Yu
---
fsck/fsck.c | 55 +++
fsck/fsck.h | 3 ++-
include/f2fs_fs.h | 6 +++
Previously, once fsck.f2fs detects that directory missed '.' or
'..' dirent, it tags inode w/ F2FS_INLINE_DOTS flag, and expects
f2fs kernel module can repaire it online during it runs to lookup()
on target directory.
This patch abandons previous implementation, and do repaires directly.
Reviewed
Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(),
f2fs_move_file_range(), and f2fs_defragment_range() missed to
check atomic_write status, which may cause potential race issue,
fix it.
Cc: sta...@vger.kernel.org
Signed-off-by: Chao Yu
---
fs/f2fs/file.c | 13 -
1 file changed,
On 2024/9/4 10:52, Daeho Jeong wrote:
On Tue, Sep 3, 2024 at 7:26 PM Chao Yu wrote:
On 2024/9/4 1:07, Daeho Jeong wrote:
On Mon, Sep 2, 2024 at 3:08 AM Chao Yu wrote:
On 2024/8/27 4:23, Daeho Jeong wrote:
From: Daeho Jeong
Keep atomic file clean while updating and make it dirtied during
On 2024/9/3 14:06, wangzijie wrote:
From: Chao Yu via Linux-f2fs-devel
On 2024/8/27 14:22, wangzijie wrote:
Thread A
-dquot_initialize
-dqget
-f2fs_dquot_acquire
-v2_read_dquot
-qtree_read_dquot
-find_tree_dqentry
-f2fs_quota_read
-read_cache_page_gfp
On 2024/9/4 5:20, Jaegeuk Kim wrote:
On 09/03, Chao Yu wrote:
On 2024/9/2 21:01, Julian Sun wrote:
On Mon, 2024-09-02 at 16:13 +0800, Chao Yu wrote:
On 2024/8/29 0:54, Julian Sun wrote:
Hi, all.
Recently syzbot reported a bug as following:
kernel BUG at fs/f2fs/inode.c:896!
CPU: 1 UID: 0 PI
On 2024/9/4 22:56, Daeho Jeong wrote:
On Tue, Sep 3, 2024 at 8:35 PM Chao Yu wrote:
On 2024/9/4 10:52, Daeho Jeong wrote:
On Tue, Sep 3, 2024 at 7:26 PM Chao Yu wrote:
On 2024/9/4 1:07, Daeho Jeong wrote:
On Mon, Sep 2, 2024 at 3:08 AM Chao Yu wrote:
On 2024/8/27 4:23, Daeho Jeong wrot
On 2024/9/4 1:31, Daeho Jeong wrote:
From: Daeho Jeong
The conversion between cpu and little endian is incorrect.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
#syz invalid
Becuase commit "f2fs: atomic: fix to not allow GC to pollute atomic_file" has
been dropped.
On 2024/8/17 8:27, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:9e6869691724 Add linux-next specific files for 20240812
git tree: linux-next
console outp
#syz fix: f2fs: atomic: fix to forbid dio in atomic_file
On 2024/8/14 19:51, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:9e6869691724 Add linux-next specific files for 20240812
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14
#syz invalid
Becuase commit "f2fs: atomic: fix to not allow GC to pollute atomic_file" has
been dropped from linux-next git repo.
On 2024/8/14 4:49, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:9e6869691724 Add linux-next specific files for 20240812
git tree:
#syz invalid
Becuase commit "f2fs: atomic: fix to not allow GC to pollute atomic_file" has
been dropped from linux-next git repo.
On 2024/8/16 17:16, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:9e6869691724 Add linux-next specific files for 20240812
git tree:
On 2024/9/4 9:12, Daejun Park wrote:
This patch enables support for write hints by segment type.
Signed-off-by: Daejun Park
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourc
On 2024/9/5 13:24, Daejun Park wrote:
This patch addresses the problem that when using LFS mode, unused blocks
may occur in f2fs_map_blocks() during block allocation for dio writes.
If a new section is allocated during block allocation, it will not be
included in the map struct by map_is_mergeab
On 2024/9/6 5:20, Daeho Jeong wrote:
From: Daeho Jeong
Fixed wrong endian conversions related to i_flags.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Since we don't have any GC on device side for zoned devices, need more
aggressive BG GC. So, tune the parameters for that.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linu
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Now we do readahead for a full section by not considering
migration_granularity and it triggers unnecessary read. So, make it read
with the correct amount.
Signed-off-by: Daeho Jeong
---
fs/f2fs/gc.c | 33 --
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
For the fine tuning of GC behavior, add reserved_segments sysfs node.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sour
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Need bigger BG GC migration granularity when free section is running
low.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.
syzbot reports a f2fs bug as below:
kernel BUG at fs/f2fs/inode.c:896!
RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896
Call Trace:
evict+0x532/0x950 fs/inode.c:704
dispose_list fs/inode.c:747 [inline]
evict_inodes+0x5f9/0x690 fs/inode.c:797
generic_shutdown_super+0x9d/0x2d0 fs/sup
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Under low free section count, we need to use FG_GC instead of BG_GC to
recover free sections.
Signed-off-by: Daeho Jeong
---
fs/f2fs/f2fs.h | 1 +
fs/f2fs/gc.c | 24 +---
2 files changed, 18 insertions(+), 7 de
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Added control knobs for gc_no_zoned_gc_percent and
gc_boost_zoned_gc_percent.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@li
On 2024/9/6 16:31, Wu Bo wrote:
On Tue, Feb 20, 2024 at 02:50:11PM +0800, Chao Yu wrote:
On 2024/2/8 16:11, Wu Bo wrote:
On 2024/2/5 11:54, Chao Yu wrote:
How about calling f2fs_balance_fs() to double check and make sure there is
enough free space for following allocation.
if (has_no
On 2024/9/8 12:12, wangzijie wrote:
From: Chao Yu via Linux-f2fs-devel
On 2024/8/27 14:22, wangzijie wrote:
Thread A
-dquot_initialize
-dqget
-f2fs_dquot_acquire
-v2_read_dquot
-qtree_read_dquot
-find_tree_dqentry
-f2fs_quota_read
On 2024/9/7 4:23, Daeho Jeong wrote:
On Thu, Sep 5, 2024 at 7:56 PM Chao Yu wrote:
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
Now we do readahead for a full section by not considering
migration_granularity and it triggers unnecessary read. So, make it read
with the correct amou
On 2024/9/9 12:06, wangzijie wrote:
On 2024/9/8 12:12, wangzijie wrote:
From: Chao Yu via Linux-f2fs-devel
On 2024/8/27 14:22, wangzijie wrote:
Thread A
-dquot_initialize
-dqget
-f2fs_dquot_acquire
-v2_read_dquot
-qtree_read_dquot
-find_tree_dqentry
On 2024/8/30 5:52, Daeho Jeong wrote:
From: Daeho Jeong
We need to introduce a valid block ratio threshold not to trigger
excessive GC for zoned deivces. The initial value of it is 95%. So, F2FS
will stop the thread from intiating GC for sections having valid blocks
exceeding the ratio.
Signed
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
On 2024/9/9 16:19, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:89f5e14d05b4 Merge tag 'timers_urgent_for_v6.11_rc7' of gi..
git tree: upstream
console output: https://syzkaller.appspo
f2fs: fix to don't panic system for no free segment fault injection
syzbot reports a f2fs bug as below:
F2FS-fs (loop0): inject no free segment in get_new_segment of
__allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3167
F2FS-fs (loop0): Stopped filesystem due to reason: 7
[ cut h
syzbot reports a f2fs bug as below:
[ cut here ]
WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180
kernel/rcu/sync.c:177
CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted
6.10.0-syzkaller-12562-g1722389b0d86 #0
Workqueue: events destroy_super_wor
After commit 5c8764f8679e ("f2fs: fix to force buffered IO on inline_data
inode"), f2fs starts to force using buffered IO on inline_data inode.
And also, it will cause f2fs_getattr() returning invalid zeroed value on
.dio_mem_align and .dio_offset_align fields, however, STATX_DIOALIGN flag
was bee
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
On 2024/7/26 15:54, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:1722389b0d86 Merge tag 'net-6.11-rc1' of git://git.kernel...
git tree: upstream
console+strace: https://syzkaller.ap
On 2024/9/10 0:45, Daeho Jeong wrote:
From: Daeho Jeong
Removed a redundant code to set i_ext.len to zero.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https:/
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
Since we don't have any GC on device side for zoned devices, need more
aggressive BG GC. So, tune the parameters for that.
Signed-off-by: Daeho Jeong
Daeho,
What about collecting all last reviewed-by tags for each patch of this
patchs
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
We can control the scanning window granularity for GC migration. For
more frequent scanning and GC on zoned devices, we need a fine grained
control knob for it.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
__
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
For the fine tuning of GC behavior, add reserved_segments sysfs node.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sour
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
Need bigger BG GC migration window granularity when free section is
running low.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
Under low free section count, we need to use FG_GC instead of BG_GC to
recover free sections.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Lin
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
Added control knobs for gc_no_zoned_gc_percent and
gc_boost_zoned_gc_percent.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@li
On 2024/9/10 6:19, Daeho Jeong wrote:
From: Daeho Jeong
We need to introduce a valid block ratio threshold not to trigger
excessive GC for zoned deivces. The initial value of it is 95%. So, F2FS
will stop the thread from intiating GC for sections having valid blocks
exceeding the ratio.
Signed
On 2024/9/11 1:06, Eric Biggers wrote:
On Tue, Sep 10, 2024 at 08:57:53PM +0800, Chao Yu via Linux-f2fs-devel wrote:
After commit 5c8764f8679e ("f2fs: fix to force buffered IO on inline_data
inode"), f2fs starts to force using buffered IO on inline_data inode.
And also, it
On 2024/9/4 11:49, Chao Yu via Linux-f2fs-devel wrote:
On 2024/9/3 14:06, wangzijie wrote:
From: Chao Yu via Linux-f2fs-devel
On 2024/8/27 14:22, wangzijie wrote:
Thread A
-dquot_initialize
-dqget
-f2fs_dquot_acquire
-v2_read_dquot
-qtree_read_dquot
-find_tree_dqentry
On 2024/9/11 10:40, liuder...@oppo.com wrote:
From: liuderong
Remove unused parameter segno from f2fs_usable_segs_in_sec.
Signed-off-by: liuderong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforg
On 2024/9/11 10:40, liuder...@oppo.com wrote:
From: liuderong
When segs_per_sec is larger than 1, section may contain free segments,
mtime should be the mean value of each valid segments,
so introduce get_section_mtime to exclude free segments in a section.
Signed-off-by: liuderong
---
fs/f
On 2024/9/11 10:04, Hongbo Li wrote:
Is the subject of the email required to be [f2fs-dev][PATCH]?
Hongbo,
"[f2fs-dev]" prefix is added by f2fs mailing list when it forwards
your patch to someone who subscribes the list, if you receive a patch
w/o f2fs-dev prefix, it is because you Sent/Cced p
On 2024/9/11 11:57, Wu Bo wrote:
The inode in F2FS occupies an entire 4k block. For many small files, this means
they consume much more space than their actual size. Therefore, there is
significant potential to better utilize the inode block space.
Currently, F2FS has two features to make use of
On 2024/9/13 0:59, Daeho Jeong wrote:
From: Daeho Jeong
We need to migrate data blocks even though it is full to secure space
for zoned device file pinning.
Signed-off-by: Daeho Jeong
Fixes: 9703d69d9d15 ("f2fs: support file pinning for zoned devices")
Reviewed-by: Chao Yu
Thanks,
_
On 2024/9/12 21:50, kernel test robot wrote:
Hello,
kernel test robot noticed "xfstests.generic.091.fail" on:
commit: 5c8764f8679e659c5cb295af7d32279002d13735 ("f2fs: fix to force buffered IO on
inline_data inode")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
Can
Jaegeuk,
Any comments on this patch?
On 2022/8/7 18:49, Chao Yu wrote:
From: Chao Yu
Previously, we supported to account FS_CDATA_READ_IO type IO only,
in this patch, it adds to account more type IO for compressed file:
- APP_BUFFERED_CDATA_IO
- APP_MAPPED_CDATA_IO
- FS_CDATA_IO
- APP_BUFFERE
On 2021/12/30 8:59, Antoine Viallon via Linux-f2fs-devel wrote:
Some variable naming mistaskes were made in the last patch,
here is an updated version.
---
fsck/fsck.c | 9 +
fsck/fsck.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index ecd87af..9
On 2022/2/3 4:17, Daeho Jeong wrote:
From: Daeho Jeong
Added two option to f2fs_io "write" command.
- atomic_commit : atomic write & commit
- atomic_abort : atomic write & abort
Also, added an optional option {delay}, which is in ms unit and optional
only for atomic_commit and atomic_abort
On 2022/2/8 15:16, Sun Ke via Linux-f2fs-devel wrote:
f2fs has set inline_xattr as a default option, and introduced a new
option named 'noinline_xattr' for disabling default inline_xattr option.
So in _acl_get_max we need to check 'noinline_xattr' string in fs
option, otherwise we may select the
On 2022/2/15 16:27, Juhyung Park wrote:
cnt should be passed to sb_has_quota_active() instead of type to check
active quota properly.
Moreover, when the type is -1, the compiler with enough inline knowledge
can discard sb_has_quota_active() check altogether, causing a NULL pointer
dereference at
On 2022/2/25 16:22, yebin via Linux-f2fs-devel wrote:
diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
index a0e51937d92e..3de5a1343070 100644
--- a/fs/f2fs/dir.c
+++ b/fs/f2fs/dir.c
@@ -953,7 +953,7 @@ void f2fs_delete_entry(struct f2fs_dir_entry *dentry,
struct page *page,
f2fs_drop_nlink(
On 2022/2/28 11:57, Sun Ke via Linux-f2fs-devel wrote:
The test fail on f2fs:
xattr names and values after second fsync log replay:
# file: SCRATCH_MNT/foobar
+user.attr1="val1"
user.attr3="val3"
attr1 is still there after log replay.
I guess it is f2fs's special feature t
On 2022/3/11 17:43, Sun Ke via Linux-f2fs-devel wrote:
The test fail on f2fs:
xattr names and values after second fsync log replay:
# file: SCRATCH_MNT/foobar
+user.attr1="val1"
user.attr3="val3"
attr1 is still there after log replay. f2fs doesn't support fs-op level
trans
On 2022/3/23 10:28, Jaegeuk Kim wrote:
This gives an information of "-g android".
Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/list
On 2024/10/9 2:05, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs tool and it can map the whole device with an extrent, not
using node blocks. The file spa
On 2024/10/12 0:44, Ye Bin wrote:
From: Ye Bin
There's issue as follows when concurrently installing the f2fs.ko
module and mounting the f2fs file system:
KASAN: null-ptr-deref in range [0x0020-0x0027]
RIP: 0010:__bio_alloc+0x2fb/0x6c0 [f2fs]
Call Trace:
f2fs_submit
On 2024/10/15 8:23, Jaegeuk Kim via Linux-f2fs-devel wrote:
It's complicated to address libc and kernel headers.
Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
htt
On 2024/10/15 5:32, Jaegeuk Kim via Linux-f2fs-devel wrote:
Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-d
This is a regression test to check whether f2fs handles dirty
data correctly when checkpoint is disabled, if lfs mode is on,
it will trigger OPU for all overwritten data, this will cost
free segments, so f2fs must account overwritten data as OPU
data when calculating free space, otherwise, it may r
metadata of compressed inode should always be consistent after file
compression, reservation, releasement and decompression, let's add
a testcase to check it.
Cc: Jaegeuk Kim
Cc: Qi Han
Signed-off-by: Chao Yu
---
tests/f2fs/007 | 116 +
tests/f2f
On 2024/10/12 6:49, Jaegeuk Kim via Linux-f2fs-devel wrote:
This adds a way to boost read performance by giving fadvise.
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/tools/f2fs_io/f2fs_
It will trigger system panic w/ testcase in [1]:
[ cut here ]
kernel BUG at fs/f2fs/segment.c:2752!
RIP: 0010:new_curseg+0xc81/0x2110
Call Trace:
f2fs_allocate_data_block+0x1c91/0x4540
do_write_page+0x163/0xdf0
f2fs_outplace_write_data+0x1aa/0x340
f2fs_do_write_data_pag
On 2024/10/7 19:46, Thorsten Blum wrote:
Use struct_size() to calculate the number of bytes to allocate for a
cloned acl.
Signed-off-by: Thorsten Blum
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourcefo
On 2024/9/24 17:56, Liao Yuanhong wrote:
The f2fs-tools support manual configuration of rsvd and ovp rate. In cases
where only a small rsvd is set, the automatically calculated ovp rate can
be very large, resulting in the reserved space of the entire file system
being almost the same as before, f
On 2024/10/1 6:58, Jaegeuk Kim wrote:
On 09/26, Matthew Wilcox wrote:
On Thu, Sep 26, 2024 at 04:01:21PM +0200, Pankaj Raghav (Samsung) wrote:
Convert wbc_account_cgroup_owner() to take a folio instead of a page,
and convert all callers to pass a folio directly except f2fs.
Convert the page to
The bug related to this regression testcase has been fixed by commit
b2c160f4f3cf ("f2fs: atomic: fix to forbid dio in atomic_file"), let's
add missing _fixed_by_kernel_commit line for this testcase.
Cc: Jaegeuk Kim
Cc: Daeho Jeong
Signed-off-by: Chao Yu
---
tests/f2fs/004 | 3 +++
1 file chan
On 2024/9/18 16:44, Qi Han wrote:
creating a large files during checkpoint disable until it runs out of
space and then delete it, then remount to enable checkpoint again, and
then unmount the filesystem triggers the f2fs_bug_on as below:
[ cut here ]
kernel BUG at fs/f2fs
On 2024/9/29 14:17, LongPing Wei wrote:
Signed-off-by: LongPing Wei
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
On 2024/9/29 16:00, Qi Han wrote:
After release a file and subsequently reserve it, the FSCK flag is set
when the file is deleted, as shown in the following backtrace:
F2FS-fs (dm-48): Inconsistent i_blocks, ino:401231, iblocks:1448, sectors:1472
fs_rec_info_write_type+0x58/0x274
f2fs_rec_info_w
On 2024/9/26 5:52, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs tool and it can map the whole device with an extrent, not
using node blocks. The file spa
syzbot reports a f2fs bug as below:
[ cut here ]
kernel BUG at fs/f2fs/segment.c:2534!
RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534
Call Trace:
truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909
f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288
f2fs
In __get_segment_type(), __get_segment_type_6() may return
CURSEG_COLD_DATA_PINNED or CURSEG_ALL_DATA_ATGC log type, but
following f2fs_get_segment_temp() can only handle persistent
log type, fix it.
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h| 5 +++--
fs/f2fs/file.c| 4 ++--
fs/f2fs/se
This patch adds per-device stats in debugfs, the examples
are as below:
mkfs.f2fs -f -c /dev/vdc /dev/vdb
mount /dev/vdb /mnt/f2fs/
cat /sys/kernel/debug/f2fs/status
Multidevice stats:
[seg: inusedirty full free prefree]
#0 500 40070
On 2024/10/21 10:31, LongPing Wei wrote:
This f2fs_bug_on was introduced by commit 2c1905042c8c ("f2fs: check
segment type in __f2fs_replace_block") when there were only 6 curseg types.
After commit d0b9e42ab615 ("f2fs: introduce inmem curseg") was introduced,
the condition should be changed to c
On 2024/10/21 12:48, Yongpeng Yang wrote:
In the __f2fs_init_atgc_curseg->get_atssr_segment calling,
curseg->segno is NULL_SEGNO, indicating that there is no summary
block that needs to be written.
Fixes: 093749e296e2 ("f2fs: support age threshold based garbage collection")
Signed-off-by: Yo
Hi,
Thanks for the report, I rebased this patch on top of
https://lore.kernel.org/linux-f2fs-devel/20241017012932.1570038-1-c...@kernel.org,
so there will be dependency in between these two patch.
Thanks,
On 2024/10/20 5:57, kernel test robot wrote:
Hi Chao,
kernel test robot noticed the foll
In __get_segment_type(), __get_segment_type_6() may return
CURSEG_COLD_DATA_PINNED or CURSEG_ALL_DATA_ATGC log type, but
following f2fs_get_segment_temp() can only handle persistent
log type, fix it.
Signed-off-by: Chao Yu
---
v3:
- initialize type variable in __get_segment_type()
fs/f2fs/f2fs.h
On 2024/10/22 7:18, Jaegeuk Kim wrote:
On 10/18, Chao Yu wrote:
blkzoned feature enables lfs mode by default, for data updates from
regular file, it only allow to use OPU, this patch changes to allow
to use IPU if regular file's data block locates in regular block
device, if data block locates i
On 2024/10/9 18:27, Qi Han wrote:
When the free segment is used up during CP disable, many write or
ioctl operations will get ENOSPC error codes, even if there are
still many blocks available. We can reproduce it in the following
steps:
dd if=/dev/zero of=f2fs.img bs=1M count=55
mkfs.f2fs -f f2f
On 2024/10/22 11:14, 韩棋 wrote:
在 2024/10/22 10:53, Chao Yu 写道:
On 2024/10/9 18:27, Qi Han wrote:
When the free segment is used up during CP disable, many write or
ioctl operations will get ENOSPC error codes, even if there are
still many blocks available. We can reproduce it in the following
st
syzbot reports deadlock issue of f2fs as below:
==
WARNING: possible circular locking dependency detected
6.12.0-rc3-syzkaller-00087-gc964ced77262 #0 Not tainted
--
kswapd0/79 is trying to acqui
On 2024/10/16 0:54, Daeho Jeong wrote:
From: Daeho Jeong
Now we reclaim too much space before allocating pinned space for zoned
devices.
Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel
max open zone may be larger than log header number of f2fs, for
such case, it doesn't need to wait last IO in previous zone, let's
introduce available_open_zone semaphore, and reduce it once we
submit first write IO in a zone, and increase it after completion
of last IO in the zone.
Cc: Daeho Jeon
On 2024/10/9 18:27, Qi Han wrote:
When the free segment is used up during CP disable, many write or
ioctl operations will get ENOSPC error codes, even if there are
still many blocks available. We can reproduce it in the following
steps:
dd if=/dev/zero of=f2fs.img bs=1M count=55
mkfs.f2fs -f f2f
On 2024/10/16 2:09, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs tool and it can map the whole device with an extent, not
using node blocks. The file spa
Hand over immutable flag clearing functionality from setflags to
clearflags, since the flag name is immutable rather than noimmutable.
And support setting functionality in subcommand setflags.
Signed-off-by: Chao Yu
---
man/f2fs_io.8 | 6 +++---
tools/f2fs_io/f2fs_io.c | 9 ++---
This patch supports to set or clear nocow flag in f2fs_io
Signed-off-by: Chao Yu
---
man/f2fs_io.8 | 4 ++--
tools/f2fs_io/f2fs_io.c | 10 --
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/man/f2fs_io.8 b/man/f2fs_io.8
index e58244c..5041c1b 100644
--- a/man/f
1 - 100 of 980 matches
Mail list logo
