From: patchwork-bot+f2fs@kernel.org
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: chao@kernel.org, lvc-project@linuxtesting.org,
linux-f2fs-devel@lists.sourceforge.net,
syzbot+5141f6db57a2f7614352@syzkaller.appspotmail.com,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: ensure that node info flags are always initialized
Date: Mon, 16 Dec 2024 16:40:38 +0000 [thread overview]
Message-ID: <173436723874.272389.6295491443575015321.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241212175748.1750854-1-dmantipov@yandex.ru>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 12 Dec 2024 20:57:48 +0300 you wrote:
> Syzbot has reported the following KMSAN splat:
>
> BUG: KMSAN: uninit-value in f2fs_new_node_page+0x1494/0x1630
> f2fs_new_node_page+0x1494/0x1630
> f2fs_new_inode_page+0xb9/0x100
> f2fs_init_inode_metadata+0x176/0x1e90
> f2fs_add_inline_entry+0x723/0xc90
> f2fs_do_add_link+0x48f/0xa70
> f2fs_symlink+0x6af/0xfc0
> vfs_symlink+0x1f1/0x470
> do_symlinkat+0x471/0xbc0
> __x64_sys_symlink+0xcf/0x140
> x64_sys_call+0x2fcc/0x3d90
> do_syscall_64+0xd9/0x1b0
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: ensure that node info flags are always initialized
https://git.kernel.org/jaegeuk/f2fs/c/76f01376df39
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:[~2024-12-16 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 6:09 [PATCH] f2fs: ensure that node info flags are always initialized Dmitry Antipov
2024-12-12 14:59 ` Chao Yu
2024-12-12 17:57 ` [PATCH v2] " Dmitry Antipov
2024-12-16 13:47 ` Chao Yu
2024-12-16 16:40 ` 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=173436723874.272389.6295491443575015321.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=syzbot+5141f6db57a2f7614352@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