[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172066485813.400039.14328785579752390326.b4-ty@mit.edu>
Date: Wed, 10 Jul 2024 22:35:33 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Andreas Dilger <adilger@...ger.ca>, Jan Kara <jack@...e.cz>,
Harshad Shirwadkar <harshadshirwadkar@...il.com>,
"Luis Henriques (SUSE)" <luis.henriques@...ux.dev>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] ext4: fix fast commit inode enqueueing during a full journal commit
On Wed, 29 May 2024 10:20:28 +0100, Luis Henriques (SUSE) wrote:
> Here's v3 of this fix to the fast commit enqueuing bug triggered by fstest
> generic/047. This version simplifies the previous patch version by re-using
> the i_sync_tid field in struct ext4_inode_info instead of adding a new one.
>
> The extra patch includes a few extra fixes to the tid_t type handling. Jan
> brought to my attention the fact that this sequence number may wrap, and I
> quickly found a few places in the code where the tid_geq() and tid_gt()
> helpers had to be used.
>
> [...]
The second patch in this series was applied:
[2/2] ext4: fix possible tid_t sequence overflows
commit: 63469662cc45d41705f14b4648481d5d29cf5999
Best regards,
--
Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists