On 5/26/25 16:03, Chunhai Guo wrote:
> This is a regression test case to verify whether the CP_TRIMMED_FLAG is
> properly set after performing the following steps:
> 1. mount the f2fs filesystem
> 2. create a file, write data to it, then delete the file
> 3. unmount the filesystem
> 4. verify that
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Wed, 14 May 2025 16:45:48 +0800 you wrote:
> no logic changes.
>
> Signed-off-by: Zhiguo Niu
> ---
> fs/f2fs/namei.c | 8
> fs/f2fs/super.c | 4 ++--
> 2 files changed, 6 insertions(+), 6 deletions(-)
Here i
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: [f2fs-dev,1/2] f2fs: introduce is_{meta,node}_folio
Submitter: Chao Yu
Committer: Jaegeuk Kim
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=965697
Lore l
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 23 May 2025 11:25:45 +0800 you wrote:
> Syzbot reports a f2fs bug as below:
>
> INFO: task syz-executor328:5856 blocked for more than 144 seconds.
> Not tainted 6.15.0-rc6-syzkaller-00208-g3c21441eeffc #0
> "e
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 23 May 2025 15:33:03 +0800 you wrote:
> Just cleanup, no changes.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/checkpoint.c | 4 ++--
> fs/f2fs/data.c | 2 +-
> fs/f2fs/f2fs.h | 13 +++--
> fs
Chao,
Can we add the similar path that other filesystems have?
On 05/21, Chao Yu wrote:
> fstest reports a f2fs bug:
>
> generic/363 42s ... [failed, exit status 1]- output mismatch (see
> /share/git/fstests/results//generic/363.out.bad)
> --- tests/generic/363.out 2025-01-12 21:57:40.271
Thanks, I added the patches back with this fix applied to the original patch. :)
On 05/28, Chao Yu wrote:
> syzbot report a f2fs bug as below:
>
> CPU: 0 UID: 0 PID: 5840 Comm: syz-executor138 Not tainted
> 6.15.0-rc7-next-20250523-syzkaller #0 PREEMPT(full)
> Call Trace:
>
> dump_stack_lvl+0x
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an
issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 8b56d4fb f2fs: fix to do sanity check on secti
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git
bugfix/syzbot
On 5/26/25 20:20, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:176e917e010c Add linux-next specific files for 20250523
> git tree: linux-next
> console+strace: ht
On 5/28/25 00:54, Daeho Jeong wrote:
> From: Daeho Jeong
>
> Otherwise, it doesn't work with a crash.
>
> Signed-off-by: Daeho Jeong
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lis
syzbot report a f2fs bug as below:
CPU: 0 UID: 0 PID: 5840 Comm: syz-executor138 Not tainted
6.15.0-rc7-next-20250523-syzkaller #0 PREEMPT(full)
Call Trace:
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:408 [inline]
print_report+0xd2/0x2b0 mm/kas
11 matches
Mail list logo