From: Jan Kara <jack@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jan Kara <jack@suse.com>,
y2038@lists.linaro.org, linux-fsdevel@vger.kernel.org,
Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] quota: use time64_t internally
Date: Sun, 19 Jun 2016 18:20:21 +0200 [thread overview]
Message-ID: <20160619162021.GA6882@quack2.suse.cz> (raw)
In-Reply-To: <20160617200344.2096348-1-arnd@arndb.de>
On Fri 17-06-16 22:03:16, Arnd Bergmann wrote:
> The quota subsystem has two formats, the old v1 format using architecture
> specific time_t values on the on-disk format, while the v2 format
> (introduced in Linux 2.5.16 and 2.4.22) uses fixed 64-bit little-endian.
>
> While there is no future for the v1 format beyond y2038, the v2 format
> is almost there on 32-bit architectures, as both the user interface
> and the on-disk format use 64-bit timestamps, just not the time_t
> inbetween.
>
> This changes the internal representation to use time64_t, which will
> end up doing the right thing everywhere for v2 format.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Thanks. I've added the patch to my tree and will push it to Linus in the
next merge window.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2016-06-19 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 20:03 [PATCH] quota: use time64_t internally Arnd Bergmann
2016-06-19 16:20 ` Jan Kara [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=20160619162021.GA6882@quack2.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jack@suse.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).