linux-kernel - Re: [PATCH 00/28] nios2 Linux kernel port

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 for Android: free password hash cracker in your pocket

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

Message-ID: <5354AD36.5090809@zytor.com>
Date:	Sun, 20 Apr 2014 22:31:34 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ley Foon Tan <lftan@...era.com>, Arnd Bergmann <arnd@...db.de>
CC:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, cltang@...esourcery.com
Subject: Re: [PATCH 00/28] nios2 Linux kernel port

On 04/20/2014 10:23 PM, Ley Foon Tan wrote:
> On Sat, Apr 19, 2014 at 11:30 PM, Arnd Bergmann <arnd@...db.de> wrote:
>> On Friday 18 April 2014, H. Peter Anvin wrote:
>>> Did the generic headers ever get updated to match Linus' guidance that
>>> any new architecture ports should use a 64-bit time_t?
>>
>> No, unfortunately not. With my rule that every architecture that gets
>> added needs to clean up asm-generic some more, to make it easier to add
>> the next one, we should probably do for nios2.
>>
>>         Arnd
> 
> Can you give me the documentation on this new guidance and point me
> any architecture have implemented this?
> Thanks.
> 

We implemented it in the x32 ABI for x86.  In generic code this is keyed
by COMPAT_USE_64BIT_TIME, but in your case it isn't actually a matter of
compat, so it should be easier.

See this thread including the discussion about time_t:

https://lkml.org/lkml/2011/8/26/415

	-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/