linux-kernel - Re: [PATCHv2 1/1] fs: ext4: Don't use CMA for buffer

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: <173099237652.321265.9092728480077110829.b4-ty@mit.edu>
Date: Thu,  7 Nov 2024 10:13:03 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Andreas Dilger <adilger.kernel@...ger.ca>, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, Zhaoyang Huang <huangzhaoyang@...il.com>,
        steve.kang@...soc.com, "zhaoyang.huang" <zhaoyang.huang@...soc.com>
Cc: "Theodore Ts'o" <tytso@....edu>
Subject: Re: [PATCHv2 1/1] fs: ext4: Don't use CMA for buffer_head


On Wed, 04 Sep 2024 15:53:00 +0800, zhaoyang.huang wrote:
> cma_alloc() keep failed in our system which thanks to a jh->bh->b_page
> can not be migrated out of CMA area[1] as the jh has one cp_transaction
> pending on it because of j_free > j_max_transaction_buffers[2][3][4][5][6].
> We temporarily solve this by launching jbd2_log_do_checkpoint forcefully
> somewhere. Since journal is common mechanism to all JFSs and
> cp_transaction has a little fewer opportunity to be launched, the
> cma_alloc() could be affected under the same scenario. This patch
> would like to have buffer_head of ext4 not use CMA pages when doing
> sb_getblk.
> 
> [...]

Applied, thanks!

[1/1] fs: ext4: Don't use CMA for buffer_head
      commit: ef60f4aab81d2ce5984135e6af1abcce56a425d7

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