linux-kernel - Re: [Y2038] [PATCH 00/10] Remove CURRENT_TIME and CURRENT_TIME_SEC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABeXuvqKTWQJRjuvEKFLcLzOdu3arTTEcZHoeY+ma9WqONgSMA@mail.gmail.com>
Date:	Wed, 3 Feb 2016 20:56:50 -0800
From:	Deepa Dinamani <deepa.kernel@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	y2038@...ts.linaro.org, linux-fsdevel@...r.kernel.org,
	"Theodore Ts'o" <tytso@....edu>,
	Dave Chinner <david@...morbit.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [Y2038] [PATCH 00/10] Remove CURRENT_TIME and CURRENT_TIME_SEC -
 PART 1

>> These will be the changes to the above function:
>> 1. Function will return the type y2038 safe timespec64 in [2].
>> 2. Function will use y2038 safe 64 bit functions in [2].
>> 3. Function will be extended to perform range checks in [3].
>
> I guess [2] and [3] are really independent of one another
> and can be done in either order, correct?

That is correct.
[2] and [3] are independent of each other .

We might need one more series for bug fixes though.
Or, we can merge these independently.
I will discuss this with you separately.

-Deepa