[f2fs-dev] [syzbot] [f2fs?] possible deadlock in __f2fs_ioctl (2)

2023-01-16 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:5dc4c995db9e Linux 6.2-rc4 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11cc0da148 kernel config: https://syzkaller.appspot.com/x/.config?x=2d1e01fb80d3df97 dashboard link:

[f2fs-dev] [PATCH] MAINTAINERS: update fscrypt git repo

2023-01-16 Thread Eric Biggers
From: Eric Biggers fscrypt.git is being renamed to linux.git, so update MAINTAINERS accordingly. (The reasons for the rename are to match what I'm doing for the new fsverity repo, which also involves the branch names changing to be clearer; and to avoid ambiguity with userspace tools.) As long

[f2fs-dev] [PATCH] MAINTAINERS: update fsverity git repo, list, and patchwork

2023-01-16 Thread Eric Biggers
From: Eric Biggers We're moving fsverity development to use its own git repo, mailing list, and patchwork project, instead of reusing the fscrypt ones. Update the MAINTAINERS file accordingly. Signed-off-by: Eric Biggers --- MAINTAINERS | 6 +++--- 1 file changed, 3 insertions(+), 3

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-01-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #123 from Guido (guido.iod...@gmail.com) --- (In reply to Guido from comment #113) > (In reply to Jaegeuk Kim from comment #112) > > Now I'm trying another solution: I used fstransform to format the partition > and upgrade the

[f2fs-dev] [PATCH] f2fs: fix to show discard_unit mount opt

2023-01-16 Thread Yangtao Li via Linux-f2fs-devel
Convert to show discard_unit only when has DISCARD opt. Signed-off-by: Yangtao Li --- fs/f2fs/super.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 5fc83771042d..ab8a77ffc1f4 100644 --- a/fs/f2fs/super.c +++

Re: [f2fs-dev] [PATCH v2 1/2] f2fs: fix to avoid potential memory corruption in __update_iostat_latency()

2023-01-16 Thread Yangtao Li via Linux-f2fs-devel
Hi Chao, > Maybe it's betterr to merge these two check condition as below? > > if (iotype >= NR_PAGE_TYPE) { > f2fs_bug_on(sbi, iotype != META_FLUSH); > iotype = META; > } For normal , only META_FLUSH will be greater than NR_PAGE_TYPE, there is no problem with this logic. > > For

Re: [f2fs-dev] [PATCH v2 1/2] f2fs: fix to avoid potential memory corruption in __update_iostat_latency()

2023-01-16 Thread Chao Yu
On 2023/1/16 21:02, Yangtao Li wrote: Add iotype sanity check to avoid potential memory corruption. This is to fix the compile error below: fs/f2fs/iostat.c:231 __update_iostat_latency() error: buffer overflow 'io_lat->peak_lat[type]' 3 <= 3 vim +228 fs/f2fs/iostat.c 211 static inline

[f2fs-dev] [PATCH v2 2/2] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-16 Thread Yangtao Li via Linux-f2fs-devel
Convert to use iostat_lat_type as parameter instead of raw number. BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename iotype to page_type to match the definition. Reported-by: kernel test robot Reported-by: Dan Carpenter Signed-off-by: Yangtao Li --- fs/f2fs/data.c | 4 ++--

[f2fs-dev] [PATCH v2 1/2] f2fs: fix to avoid potential memory corruption in __update_iostat_latency()

2023-01-16 Thread Yangtao Li via Linux-f2fs-devel
Add iotype sanity check to avoid potential memory corruption. This is to fix the compile error below: fs/f2fs/iostat.c:231 __update_iostat_latency() error: buffer overflow 'io_lat->peak_lat[type]' 3 <= 3 vim +228 fs/f2fs/iostat.c 211 static inline void __update_iostat_latency(struct