From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: y2038@lists.linaro.org, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jfs: use time64_t for otime
Date: Tue, 19 Jun 2018 14:06:47 -0500 [thread overview]
Message-ID: <ca7ae8eb-c458-dc3e-be3f-37cb22e3052c@oracle.com> (raw)
In-Reply-To: <20180619155110.3950450-1-arnd@arndb.de>
On 06/19/2018 10:51 AM, Arnd Bergmann wrote:
> The file creation time in the inode uses time_t which is defined differently
> on 32-bit and 64-bit architectures and deprecated. The representation in
> the inode uses an unsigned 32-bit number, but this gets wrapped around
> after year 2038 when assigned to a time_t.
>
> This changes the type to time64_t, so we can support the full range of
> timestamps between 1970 and 2106 on 32-bit systems like we do on 64-bit
> systems already, and matching what we do for the atime/ctime/mtime stamps
> since the introduction of 64-bit timestamps in VFS.
>
> Note: the otime stamp is not actually used anywhere at the moment in
> the kernel, it is just set when writing a file, so none of this really
> makes a difference unless we implement setting the btime field in the
> getattr() callback.
This looks good to me. I'll push it to linux-next and target the next
merge window.
Thanks,
Shaggy
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> fs/jfs/jfs_incore.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/jfs/jfs_incore.h b/fs/jfs/jfs_incore.h
> index 1f26d1910409..d5c46f86b2ef 100644
> --- a/fs/jfs/jfs_incore.h
> +++ b/fs/jfs/jfs_incore.h
> @@ -43,7 +43,7 @@ struct jfs_inode_info {
> pxd_t ixpxd; /* inode extent descriptor */
> dxd_t acl; /* dxd describing acl */
> dxd_t ea; /* dxd describing ea */
> - time_t otime; /* time created */
> + time64_t otime; /* time created */
> uint next_index; /* next available directory entry index */
> int acltype; /* Type of ACL */
> short btorder; /* access order */
>
prev parent reply other threads:[~2018-06-19 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:51 Arnd Bergmann
2018-06-19 19:06 ` Dave Kleikamp [this message]
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=ca7ae8eb-c458-dc3e-be3f-37cb22e3052c@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=arnd@arndb.de \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=y2038@lists.linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®