From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
syzbot+9201a61c060513d4be38@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to use f2fs_is_valid_blkaddr_raw() in do_write_page()
Date: Wed, 09 Jul 2025 18:10:19 +0000 [thread overview]
Message-ID: <175208461925.806926.9116732012355450749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701092610.511964-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 1 Jul 2025 17:26:10 +0800 you wrote:
> As syzbot reported as below:
>
> F2FS-fs (loop9): inject invalid blkaddr in f2fs_is_valid_blkaddr of do_write_page+0x277/0xb10 fs/f2fs/segment.c:3956
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:3957!
> Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
> CPU: 0 UID: 0 PID: 10538 Comm: syz-executor Not tainted 6.16.0-rc3-next-20250627-syzkaller #0 PREEMPT(full)
> Call Trace:
> <TASK>
> f2fs_outplace_write_data+0x11a/0x220 fs/f2fs/segment.c:4017
> f2fs_do_write_data_page+0x12ea/0x1a40 fs/f2fs/data.c:2752
> f2fs_write_single_data_page+0xa68/0x1680 fs/f2fs/data.c:2851
> f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline]
> __f2fs_write_data_pages fs/f2fs/data.c:3282 [inline]
> f2fs_write_data_pages+0x195b/0x3000 fs/f2fs/data.c:3309
> do_writepages+0x32b/0x550 mm/page-writeback.c:2636
> filemap_fdatawrite_wbc mm/filemap.c:386 [inline]
> __filemap_fdatawrite_range mm/filemap.c:419 [inline]
> __filemap_fdatawrite mm/filemap.c:425 [inline]
> filemap_fdatawrite+0x199/0x240 mm/filemap.c:430
> f2fs_sync_dirty_inodes+0x31f/0x830 fs/f2fs/checkpoint.c:1108
> block_operations fs/f2fs/checkpoint.c:1247 [inline]
> f2fs_write_checkpoint+0x95a/0x1df0 fs/f2fs/checkpoint.c:1638
> kill_f2fs_super+0x2c3/0x6c0 fs/f2fs/super.c:5081
> deactivate_locked_super+0xb9/0x130 fs/super.c:474
> cleanup_mnt+0x425/0x4c0 fs/namespace.c:1417
> task_work_run+0x1d4/0x260 kernel/task_work.c:227
> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
> exit_to_user_mode_loop+0xec/0x110 kernel/entry/common.c:114
> exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline]
> syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline]
> syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline]
> do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to use f2fs_is_valid_blkaddr_raw() in do_write_page()
https://git.kernel.org/jaegeuk/f2fs/c/8f4688591d96
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+9201a61c060513d4be38@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to use f2fs_is_valid_blkaddr_raw() in do_write_page()
Date: Wed, 09 Jul 2025 18:10:19 +0000 [thread overview]
Message-ID: <175208461925.806926.9116732012355450749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250701092610.511964-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 1 Jul 2025 17:26:10 +0800 you wrote:
> As syzbot reported as below:
>
> F2FS-fs (loop9): inject invalid blkaddr in f2fs_is_valid_blkaddr of do_write_page+0x277/0xb10 fs/f2fs/segment.c:3956
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:3957!
> Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
> CPU: 0 UID: 0 PID: 10538 Comm: syz-executor Not tainted 6.16.0-rc3-next-20250627-syzkaller #0 PREEMPT(full)
> Call Trace:
> <TASK>
> f2fs_outplace_write_data+0x11a/0x220 fs/f2fs/segment.c:4017
> f2fs_do_write_data_page+0x12ea/0x1a40 fs/f2fs/data.c:2752
> f2fs_write_single_data_page+0xa68/0x1680 fs/f2fs/data.c:2851
> f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline]
> __f2fs_write_data_pages fs/f2fs/data.c:3282 [inline]
> f2fs_write_data_pages+0x195b/0x3000 fs/f2fs/data.c:3309
> do_writepages+0x32b/0x550 mm/page-writeback.c:2636
> filemap_fdatawrite_wbc mm/filemap.c:386 [inline]
> __filemap_fdatawrite_range mm/filemap.c:419 [inline]
> __filemap_fdatawrite mm/filemap.c:425 [inline]
> filemap_fdatawrite+0x199/0x240 mm/filemap.c:430
> f2fs_sync_dirty_inodes+0x31f/0x830 fs/f2fs/checkpoint.c:1108
> block_operations fs/f2fs/checkpoint.c:1247 [inline]
> f2fs_write_checkpoint+0x95a/0x1df0 fs/f2fs/checkpoint.c:1638
> kill_f2fs_super+0x2c3/0x6c0 fs/f2fs/super.c:5081
> deactivate_locked_super+0xb9/0x130 fs/super.c:474
> cleanup_mnt+0x425/0x4c0 fs/namespace.c:1417
> task_work_run+0x1d4/0x260 kernel/task_work.c:227
> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
> exit_to_user_mode_loop+0xec/0x110 kernel/entry/common.c:114
> exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline]
> syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline]
> syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline]
> do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to use f2fs_is_valid_blkaddr_raw() in do_write_page()
https://git.kernel.org/jaegeuk/f2fs/c/8f4688591d96
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-09 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 9:26 [f2fs-dev] [PATCH] f2fs: fix to use f2fs_is_valid_blkaddr_raw() in do_write_page() Chao Yu via Linux-f2fs-devel
2025-07-01 9:26 ` Chao Yu
2025-07-09 18:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-07-09 18:10 ` [f2fs-dev] " patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175208461925.806926.9116732012355450749.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=syzbot+9201a61c060513d4be38@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.