linux-kernel - Re: [Y2038] [PATCH] crypto: use timespec64 for jent_get

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] [day] [month] [year] [list]

Message-ID: <2121132.qNHuddqZk8@tauon.atsec.com>
Date:	Tue, 21 Jun 2016 19:07:45 +0200
From:	Stephan Mueller <smueller@...onox.de>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Alexander Kuleshov <kuleshovmail@...il.com>,
	y2038 Mailman List <y2038@...ts.linaro.org>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-crypto@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Kees Cook <keescook@...omium.org>
Subject: Re: [Y2038] [PATCH] crypto: use timespec64 for jent_get_nstime

Am Dienstag, 21. Juni 2016, 18:51:32 schrieb Stephan Mueller:

Hi,

> > So.. again, I'd avoid using the "fast" accessor unless there is a
> > clear need or obvious benefit. Which should be documented.
> 
> So, you suggest ktime_get_raw_ns? If yes, let me test that for one use case.

I tested ktime_get_raw_ns and it exhibits the same results as 
ktime_get_raw_fast_ns and RDTSC. So, I see no objections in using 
ktime_get_raw_ns.

Ciao
Stephan