linux-ext4 - Re: [PATCH] ext4: don't track ranges in fast

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: <172066485815.400039.14789389889049658262.b4-ty@mit.edu>
Date: Wed, 10 Jul 2024 22:35:31 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Andreas Dilger <adilger@...ger.ca>,
        "Luis Henriques (SUSE)" <luis.henriques@...ux.dev>
Cc: "Theodore Ts'o" <tytso@....edu>, Ben Hutchings <ben@...adent.org.uk>,
        Harshad Shirwadkar <harshadshirwadkar@...il.com>,
        linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: don't track ranges in fast_commit if inode has inlined data


On Tue, 18 Jun 2024 15:43:12 +0100, Luis Henriques (SUSE) wrote:
> When fast-commit needs to track ranges, it has to handle inodes that have
> inlined data in a different way because ext4_fc_write_inode_data(), in the
> actual commit path, will attempt to map the required blocks for the range.
> However, inodes that have inlined data will have it's data stored in
> inode->i_block and, eventually, in the extended attribute space.
> 
> Unfortunately, because fast commit doesn't currently support extended
> attributes, the solution is to mark this commit as ineligible.
> 
> [...]

Applied, thanks!

[1/1] ext4: don't track ranges in fast_commit if inode has inlined data
      commit: 7882b0187bbeb647967a7b5998ce4ad26ef68a9a

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