linux-ext4 - Re: [PATCH v2] ext4: dax: keep orphan list before truncate overflow allocated blocks

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: <172554793832.1268668.11709771294589119561.b4-ty@mit.edu>
Date: Thu,  5 Sep 2024 10:53:48 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: adilger.kernel@...ger.ca, jack@...e.cz,
        Yang Erkun <yangerkun@...weicloud.com>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        yangerkun@...wei.com
Subject: Re: [PATCH v2] ext4: dax: keep orphan list before truncate overflow allocated blocks


On Thu, 29 Aug 2024 19:02:22 +0800, Yang Erkun wrote:
> Any extending write for ext4 requires the inode to be placed on the
> orphan list before the actual write. In addition, the inode can be
> actually removed from the orphan list only after all writes are
> completed. Otherwise we'd leave allocated blocks beyond i_disksize if we
> could not copy all the data into allocated block and e2fsck would
> complain.
> 
> [...]

Applied, thanks!

[1/1] ext4: dax: keep orphan list before truncate overflow allocated blocks
      commit: 59efe53e380ee305ec11378233adb6aaebe1856c

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