From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Abinash Singh <abinashlalotra@gmail.com>
Cc: syzbot+b8c1d60e95df65e827d4@syzkaller.appspotmail.com,
abinashsinghlalotra@gmail.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: fix KMSAN uninit-value in extent_info usage
Date: Wed, 09 Jul 2025 18:10:17 +0000 [thread overview]
Message-ID: <175208461775.806926.5771206803640875026.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250625110537.22806-1-abinashsinghlalotra@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 25 Jun 2025 16:35:37 +0530 you wrote:
> KMSAN reported a use of uninitialized value in `__is_extent_mergeable()`
> and `__is_back_mergeable()` via the read extent tree path.
>
> The root cause is that `get_read_extent_info()` only initializes three
> fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the
> remaining fields uninitialized. This leads to undefined behavior
> when those fields are accessed later, especially during
> extent merging.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4] f2fs: fix KMSAN uninit-value in extent_info usage
https://git.kernel.org/jaegeuk/f2fs/c/154467f4ad03
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: Abinash Singh <abinashlalotra@gmail.com>
Cc: chao@kernel.org,
syzbot+b8c1d60e95df65e827d4@syzkaller.appspotmail.com,
abinashsinghlalotra@gmail.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: fix KMSAN uninit-value in extent_info usage
Date: Wed, 09 Jul 2025 18:10:17 +0000 [thread overview]
Message-ID: <175208461775.806926.5771206803640875026.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250625110537.22806-1-abinashsinghlalotra@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 25 Jun 2025 16:35:37 +0530 you wrote:
> KMSAN reported a use of uninitialized value in `__is_extent_mergeable()`
> and `__is_back_mergeable()` via the read extent tree path.
>
> The root cause is that `get_read_extent_info()` only initializes three
> fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the
> remaining fields uninitialized. This leads to undefined behavior
> when those fields are accessed later, especially during
> extent merging.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4] f2fs: fix KMSAN uninit-value in extent_info usage
https://git.kernel.org/jaegeuk/f2fs/c/154467f4ad03
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: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 12:09 [f2fs-dev] [PATCH v2] f2fs: fix KMSAN uninit-value in extent_info usage Abinash Singh
2025-06-19 12:09 ` Abinash Singh
2025-06-24 14:16 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-06-24 14:16 ` Chao Yu
2025-06-24 17:09 ` [f2fs-dev] [PATCH v3] " Abinash Singh
2025-06-24 17:09 ` Abinash Singh
2025-06-25 2:19 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-06-25 2:19 ` Chao Yu
2025-06-25 11:05 ` [f2fs-dev] [PATCH v4] " Abinash Singh
2025-06-25 11:05 ` Abinash Singh
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=175208461775.806926.5771206803640875026.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=abinashlalotra@gmail.com \
--cc=abinashsinghlalotra@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=syzbot+b8c1d60e95df65e827d4@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.