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: <167678522163.2723470.4254795729575378394.b4-ty@mit.edu>
Date:   Sun, 19 Feb 2023 00:40:54 -0500
From:   "Theodore Ts'o" <tytso@....edu>
To:     jack@...e.com, zhanchengbin <zhanchengbin1@...wei.com>
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        liuzhiqiang26@...wei.com, yebin10@...wei.com, yi.zhang@...wei.com,
        linfeilong@...wei.com
Subject: Re: [PATCH] ext4: fix inode tree inconsistency caused by ENOMEM

On Tue, 3 Jan 2023 10:28:12 +0800, zhanchengbin wrote:
> If ENOMEM fails when the extent is splitting, we need to restore the length
> of the split extent.
> In the ext4_split_extent_at function, only in ext4_ext_create_new_leaf will
> it alloc memory and change the shape of the extent tree,even if an ENOMEM
> is returned at this time, the extent tree is still self-consistent, Just
> restore the split extent lens in the function ext4_split_extent_at.
> 
> [...]

Applied, thanks!

[1/1] ext4: fix inode tree inconsistency caused by ENOMEM
      commit: 3f5424790d4377839093b68c12b130077a4e4510

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ