From: Arnd Bergmann <arnd@arndb.de>
To: Tina Ruchandani <ruchandani.tina@gmail.com>
Cc: linux-afs@lists.infradead.org, dhowells@redhat.com,
linux-kernel@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [PATCH] AFS: Correctly use 64-bit time for UUID
Date: Thu, 05 Nov 2015 17:25:16 +0100 [thread overview]
Message-ID: <5209604.j5CNYtQLTz@wuerfel> (raw)
In-Reply-To: <20151030085101.GA3306@tina-laptop>
On Friday 30 October 2015 01:51:01 Tina Ruchandani wrote:
> UUID calculation uses 'struct timespec' whose seconds will overflow
> in year 2038 and beyond for 32-bit systems. This patch removes the
> dependency on 'struct timespec' by using ktime_get_real().
> While the patch does not fix a 'bug' as such, it is part of a larger
> effort to remove instances of 'struct timespec' and other data-structures
> suffering from y2038 problem from the kernel.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Tina Ruchandani <ruchandani.tina@gmail.com>
>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
David, I'm applying this into my y2038 tree so I don't forget about
it, but I'd prefer if you can pick it up for AFS in 4.5.
Arnd
next prev parent reply other threads:[~2015-11-05 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 8:51 [PATCH] AFS: Correctly use 64-bit time for UUID Tina Ruchandani
2015-11-05 16:25 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-11 13:44 [PATCH] afs: correctly " Arnd Bergmann
2017-01-11 13:51 ` David Howells
2017-01-11 14:03 ` Arnd Bergmann
2017-01-11 14:47 ` David Howells
2017-01-11 15:55 ` Arnd Bergmann
2015-01-29 5:53 [PATCH] AFS: Correctly " Tina Ruchandani
2015-02-11 13:52 ` David Howells
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=5209604.j5CNYtQLTz@wuerfel \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruchandani.tina@gmail.com \
--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).