From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: syzbot+b9c7ffd609c3f09416ab@syzkaller.appspotmail.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on node footer for non inode dnode
Date: Tue, 02 Sep 2025 20:20:08 +0000 [thread overview]
Message-ID: <175684440854.425353.17772733460715458985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250823054534.41037-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 23 Aug 2025 13:45:34 +0800 you wrote:
> As syzbot reported below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/file.c:1243!
> Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
> CPU: 0 UID: 0 PID: 5354 Comm: syz.0.0 Not tainted 6.17.0-rc1-syzkaller-00211-g90d970cade8e #0 PREEMPT(full)
> RIP: 0010:f2fs_truncate_hole+0x69e/0x6c0 fs/f2fs/file.c:1243
> Call Trace:
> <TASK>
> f2fs_punch_hole+0x2db/0x330 fs/f2fs/file.c:1306
> f2fs_fallocate+0x546/0x990 fs/f2fs/file.c:2018
> vfs_fallocate+0x666/0x7e0 fs/open.c:342
> ksys_fallocate fs/open.c:366 [inline]
> __do_sys_fallocate fs/open.c:371 [inline]
> __se_sys_fallocate fs/open.c:369 [inline]
> __x64_sys_fallocate+0xc0/0x110 fs/open.c:369
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f1e65f8ebe9
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to do sanity check on node footer for non inode dnode
https://git.kernel.org/jaegeuk/f2fs/c/c18ecd99e0c7
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+b9c7ffd609c3f09416ab@syzkaller.appspotmail.com,
stable@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on node footer for non inode dnode
Date: Tue, 02 Sep 2025 20:20:08 +0000 [thread overview]
Message-ID: <175684440854.425353.17772733460715458985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250823054534.41037-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 23 Aug 2025 13:45:34 +0800 you wrote:
> As syzbot reported below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/file.c:1243!
> Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
> CPU: 0 UID: 0 PID: 5354 Comm: syz.0.0 Not tainted 6.17.0-rc1-syzkaller-00211-g90d970cade8e #0 PREEMPT(full)
> RIP: 0010:f2fs_truncate_hole+0x69e/0x6c0 fs/f2fs/file.c:1243
> Call Trace:
> <TASK>
> f2fs_punch_hole+0x2db/0x330 fs/f2fs/file.c:1306
> f2fs_fallocate+0x546/0x990 fs/f2fs/file.c:2018
> vfs_fallocate+0x666/0x7e0 fs/open.c:342
> ksys_fallocate fs/open.c:366 [inline]
> __do_sys_fallocate fs/open.c:371 [inline]
> __se_sys_fallocate fs/open.c:369 [inline]
> __x64_sys_fallocate+0xc0/0x110 fs/open.c:369
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f1e65f8ebe9
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to do sanity check on node footer for non inode dnode
https://git.kernel.org/jaegeuk/f2fs/c/c18ecd99e0c7
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-09-02 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 5:45 [f2fs-dev] [PATCH] f2fs: fix to do sanity check on node footer for non inode dnode Chao Yu via Linux-f2fs-devel
2025-08-23 5:45 ` Chao Yu
2025-09-02 20:20 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-09-02 20:20 ` [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=175684440854.425353.17772733460715458985.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=stable@kernel.org \
--cc=syzbot+b9c7ffd609c3f09416ab@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.