From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+601018296973a481f302@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] Revert "f2fs: fix to do sanity check on extent cache correctly"
Date: Mon, 14 Aug 2023 20:50:22 +0000 [thread overview]
Message-ID: <169204622238.5033.822780908633322584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230720112953.3764050-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 20 Jul 2023 19:29:53 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> UBSAN: array-index-out-of-bounds in fs/f2fs/f2fs.h:3275:19
> index 1409 is out of range for type '__le32[923]' (aka 'unsigned int[923]')
> Call Trace:
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
> ubsan_epilogue lib/ubsan.c:217 [inline]
> __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348
> inline_data_addr fs/f2fs/f2fs.h:3275 [inline]
> __recover_inline_status fs/f2fs/inode.c:113 [inline]
> do_read_inode fs/f2fs/inode.c:480 [inline]
> f2fs_iget+0x4730/0x48b0 fs/f2fs/inode.c:604
> f2fs_fill_super+0x640e/0x80c0 fs/f2fs/super.c:4601
> mount_bdev+0x276/0x3b0 fs/super.c:1391
> legacy_get_tree+0xef/0x190 fs/fs_context.c:611
> vfs_get_tree+0x8c/0x270 fs/super.c:1519
> do_new_mount+0x28f/0xae0 fs/namespace.c:3335
> do_mount fs/namespace.c:3675 [inline]
> __do_sys_mount fs/namespace.c:3884 [inline]
> __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [f2fs-dev] Revert "f2fs: fix to do sanity check on extent cache correctly"
https://git.kernel.org/jaegeuk/f2fs/c/958ccbbf1ce7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-14 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:29 Chao Yu
2023-08-14 20:50 ` patchwork-bot+f2fs [this message]
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=169204622238.5033.822780908633322584.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+601018296973a481f302@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome