linux-kernel - Re: RFD: x32 ABI system call numbers

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: <CA+55aFwNpvMYF8=xmSOxmt5rj=wNFaGWJkNZQXw2fn4fW0rXHw@mail.gmail.com>
Date:	Fri, 26 Aug 2011 18:45:45 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"H.J. Lu" <hjl.tools@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: RFD: x32 ABI system call numbers

On Fri, Aug 26, 2011 at 6:35 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> Y2038 is certainly the single biggest issue here, and I fully admit to
> not having a good answer on that one.  Note that applies to every single
> 32-bit ABI in the Linux kernel, including asm-generic which is used by
> all brand new architectures.

So I've had journalists ask me about it, and I've always said that by
the time 2038 rolls around, we'll all be using 64-bit CPU's.

Which I think is a reasonable answer.

But if those 64-bit CPU's are then running some ULP32 "fast mode",
then that answer goes out the window. And I really think it's
fundamentally wrong to have "off_t" and "time_t" be 32-bit in this day
and age.  I'd hate to introduce a new mode like that. It just makes me
go "Eww".

                         Linus
--
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/