linux-ext4 - Re: [PATCH] ext4: fix extent status tree race in writeback error recovery path

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]

Date:   Thu, 14 Jul 2022 10:57:52 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     enwlinux@...il.com, linux-ext4@...r.kernel.org
Cc:     "Theodore Ts'o" <tytso@....edu>, yebin10@...wei.com
Subject: Re: [PATCH] ext4: fix extent status tree race in writeback error recovery path

On Wed, 15 Jun 2022 12:05:30 -0400, Eric Whitney wrote:
> A race can occur in the unlikely event ext4 is unable to allocate a
> physical cluster for a delayed allocation in a bigalloc file system
> during writeback.  Failure to allocate a cluster forces error recovery
> that includes a call to mpage_release_unused_pages().  That function
> removes any corresponding delayed allocated blocks from the extent
> status tree.  If a new delayed write is in progress on the same cluster
> simultaneously, resulting in the addition of an new extent containing
> one or more blocks in that cluster to the extent status tree, delayed
> block accounting can be thrown off if that delayed write then encounters
> a similar cluster allocation failure during future writeback.
> 
> [...]

Applied, thanks!

[1/1] ext4: fix extent status tree race in writeback error recovery path
      commit: 8e469e57340049d4735b71660d29bd4fd3ae1607

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