Received-SPF: pass (google.com: domain of linux-ext4+bounces-2146-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Thu, 18 Apr 2024 14:32:34 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] misc: add 2038 timestamp support
Message-ID: <20240418183234.GA3374174@mit.edu>
References: <20230927054016.16645-1-adilger@dilger.ca>
 <20240418143611.GA3373668@mit.edu>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240418143611.GA3373668@mit.edu>

On Thu, Apr 18, 2024 at 10:36:11AM -0400, Theodore Ts'o wrote:
> 
> I had recently taken this patch, but I've since found that it was
> causing a number of problems.  These have been fixed on the next
> branch, but if you have your own build of e2fsprogs, you might want to
> make sure you have these two fixups.  The second is especially
> important if you plan to use debugfs's set_super_value command on
> customer file systems....

One more commit that's needed to fix post-2038 timestamps:

commit 8b37e89f850610d51b7550ac34b8912b3000ced5
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Thu Apr 18 14:16:55 2024 -0400

    debugfs: fix printing post-2038 inode timestamps
    
    Debugfs's stat command called ext2fs_inode_xtime_get() with a struct
    inode * instead of a struct large_inode *.  As a result, printing
    inode timestamps will be incorrect if the time value is larger than
    2**32.
    
    Fixes: ca8bc9240a00 ("Add post-2038 timestamp support to e2fsprogs")
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

						- Ted