linux-ext4 - Re: [PATCH 1/2] ext4: always allocate blocks only from groups inode can use

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 for Android: free password hash cracker in your pocket

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

Message-ID: <176962347640.1138505.1021788434907927289.b4-ty@mit.edu>
Date: Wed, 28 Jan 2026 13:05:00 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Jan Kara <jack@...e.cz>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        Baokun Li <libaokun1@...wei.com>, Pedro Falcato <pfalcato@...e.de>,
        Zhang Yi <yi.zhang@...wei.com>
Subject: Re: [PATCH 1/2] ext4: always allocate blocks only from groups inode can use


On Wed, 14 Jan 2026 19:28:18 +0100, Jan Kara wrote:
> For filesystems with more than 2^32 blocks inodes using indirect block
> based format cannot use blocks beyond the 32-bit limit.
> ext4_mb_scan_groups_linear() takes care to not select these unsupported
> groups for such inodes however other functions selecting groups for
> allocation don't. So far this is harmless because the other selection
> functions are used only with mb_optimize_scan and this is currently
> disabled for inodes with indirect blocks however in the following patch
> we want to enable mb_optimize_scan regardless of inode format.
> 
> [...]

Applied, thanks!

[1/2] ext4: always allocate blocks only from groups inode can use
      commit: 4865c768b563deff1b6a6384e74a62f143427b42
[2/2] ext4: use optimized mballoc scanning regardless of inode format
      commit: 3574c322b1d0eb32dbd76b469cb08f9a67641599

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