linux-kernel - Re: [f2fs-dev] [PATCH v4] f2fs: fix KMSAN uninit-value in extent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <175208461775.806926.5771206803640875026.git-patchwork-notify@kernel.org>
Date: Wed, 09 Jul 2025 18:10:17 +0000
From: patchwork-bot+f2fs@...nel.org
To: Abinash Singh <abinashlalotra@...il.com>
Cc: chao@...nel.org, syzbot+b8c1d60e95df65e827d4@...kaller.appspotmail.com,
 abinashsinghlalotra@...il.com, linux-kernel@...r.kernel.org,
 linux-f2fs-devel@...ts.sourceforge.net, jaegeuk@...nel.org
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: fix KMSAN uninit-value in extent_info
 usage

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.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