linux-kernel - Re: [PATCH v2] ext4: refresh inline data size before write operations

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: <176340680640.138575.9087089832680529039.b4-ty@mit.edu>
Date: Mon, 17 Nov 2025 14:13:32 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: adilger.kernel@...ger.ca, Deepanshu Kartikey <kartikey406@...il.com>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        syzbot+f3185be57d7e8dda32b8@...kaller.appspotmail.com,
        stable@...nel.org
Subject: Re: [PATCH v2] ext4: refresh inline data size before write operations


On Mon, 20 Oct 2025 11:39:36 +0530, Deepanshu Kartikey wrote:
> The cached ei->i_inline_size can become stale between the initial size
> check and when ext4_update_inline_data()/ext4_create_inline_data() use
> it. Although ext4_get_max_inline_size() reads the correct value at the
> time of the check, concurrent xattr operations can modify i_inline_size
> before ext4_write_lock_xattr() is acquired.
> 
> This causes ext4_update_inline_data() and ext4_create_inline_data() to
> work with stale capacity values, leading to a BUG_ON() crash in
> ext4_write_inline_data():
> 
> [...]

Applied, thanks!

[1/1] ext4: refresh inline data size before write operations
      commit: 892e1cf17555735e9d021ab036c36bc7b58b0e3b

Best regards,
-- 
Theodore Ts'o <tytso@....edu>