[f2fs-dev] [linux-next:master] BUILD REGRESSION 1870cdc0e8dee32e3c221704a2977898ba4c10e8

2024-03-01 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 1870cdc0e8dee32e3c221704a2977898ba4c10e8 Add linux-next specific files for 20240301 Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- arm-randconfig-003-20240301 | `-- drivers

Re: [f2fs-dev] [bug report]WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 iomap_iter+0x32b observed with blktests zbd/010

2024-03-01 Thread Bart Van Assche
On 2/29/24 23:49, Yi Zhang wrote: Bisect shows it was introduced with the below commit: commit dbf8e63f48af48f3f0a069fc971c9826312dbfc1 Author: Eunhee Rho Date: Mon Aug 1 13:40:02 2022 +0900 f2fs: remove device type check for direct IO (+Eunhee) Thank you Yi for having bisected this

[f2fs-dev] [PATCH] f2fs: fix to check result of new_curseg in f2fs_allocate_segment_for_resize

2024-03-01 Thread Zhiguo Niu
new_curseg may return error if get_new_segment fail, so its result should be check in its caller f2fs_allocate_segment_for_resize, alos pass this results to free_segment_range. Signed-off-by: Zhiguo Niu --- fs/f2fs/f2fs.h| 2 +- fs/f2fs/gc.c | 7 +-- fs/f2fs/segment.c | 9 +++--

Re: [f2fs-dev] [External Mail]Re: [PATCH v3] f2fs-tools: fix to check loop device for non-root users

2024-03-01 Thread 黄佳男 via Linux-f2fs-devel
On 2024/3/1 16:39, Juhyung Park wrote: > [外部邮件] 此邮件来源于小米公司外部,请谨慎处理。若对邮件安全性存疑,请将邮件转发给mi...@xiaomi.com进行反馈 > > Hi Huang and Chao. > > I feel like this special loopback handling alongside Chao's > 14197d546b93 on f2fs-tools is just unnecessarily complicating the code > flow. > We're now doing what, lo

Re: [f2fs-dev] [PATCH v3] f2fs-tools: fix to check loop device for non-root users

2024-03-01 Thread Juhyung Park
Hi Huang and Chao. I feel like this special loopback handling alongside Chao's 14197d546b93 on f2fs-tools is just unnecessarily complicating the code flow. We're now doing what, lookup to /sys, parse original backing file, remove trailing newline char, stat()'ing it to make sure it exists? What i

[f2fs-dev] [PATCH 1/2] f2fs: fix to check return value __allocate_new_segment

2024-03-01 Thread Zhiguo Niu
__allocate_new_segment may return error when get_new_segment fails, so its caller should check its return value. Signed-off-by: Zhiguo Niu --- fs/f2fs/f2fs.h | 2 +- fs/f2fs/recovery.c | 2 +- fs/f2fs/segment.c | 7 +-- 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/fs/f

[f2fs-dev] [PATCH 2/2] f2fs: fix to check return value of f2fs_gc_range

2024-03-01 Thread Zhiguo Niu
f2fs_gc_range may return error, so its caller f2fs_allocate_pinning_section should determine whether to do retry based on ist return value. Also just do f2fs_gc_range when f2fs_allocate_new_section return -EAGAIN, and check cp error case in f2fs_gc_range. Signed-off-by: Zhiguo Niu --- fs/f2fs/g