linux-kernel - Re: [PATCH v2] ext4: correct best extent lstart adjustment logic

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: <170861726753.823885.11358303915766853695.b4-ty@mit.edu>
Date: Thu, 22 Feb 2024 10:54:31 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4@...r.kernel.org, Baokun Li <libaokun1@...wei.com>
Cc: "Theodore Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca, jack@...e.cz,
        ritesh.list@...il.com, ojaswin@...ux.ibm.com,
        linux-kernel@...r.kernel.org, yi.zhang@...wei.com,
        yangerkun@...wei.com, chengzhihao1@...wei.com, yukuai3@...wei.com,
        stable@...nel.org
Subject: Re: [PATCH v2] ext4: correct best extent lstart adjustment logic


On Thu, 01 Feb 2024 22:18:45 +0800, Baokun Li wrote:
> When yangerkun review commit 93cdf49f6eca ("ext4: Fix best extent lstart
> adjustment logic in ext4_mb_new_inode_pa()"), it was found that the best
> extent did not completely cover the original request after adjusting the
> best extent lstart in ext4_mb_new_inode_pa() as follows:
> 
>   original request: 2/10(8)
>   normalized request: 0/64(64)
>   best extent: 0/9(9)
> 
> [...]

Applied, thanks!

[1/1] ext4: correct best extent lstart adjustment logic
      commit: 4fbf8bc733d14bceb16dda46a3f5e19c6a9621c5

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