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
Date: Thu, 18 Apr 2024 14:32:34 -0400 [thread overview]
Message-ID: <20240418183234.GA3374174@mit.edu> (raw)
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
next prev parent reply other threads:[~2024-04-18 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 5:40 [PATCH] misc: add 2038 timestamp support Andreas Dilger
2024-04-01 21:29 ` Andreas Dilger
2024-04-17 2:03 ` Theodore Ts'o
2024-04-18 14:36 ` Theodore Ts'o
2024-04-18 18:32 ` Theodore Ts'o [this message]
2024-04-18 22:04 ` Andreas Dilger
2024-04-19 3:46 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240418183234.GA3374174@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.