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]

Date:	Mon, 29 Aug 2011 21:17:19 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	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 Mon, Aug 29, 2011 at 09:01:37PM +0200, Geert Uytterhoeven wrote:
> On Sat, Aug 27, 2011 at 03:42, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> > time_t really *should* be 64-bit, the same way "off_t" should be. If
> > it's not, there's something wrong.
> 
> Which will break all this non-portable 32-bit-only source code x32 was invented
> for in the first place?
> Someone will pass a time_t or off_t and an innocent pointer to a custom
> printf-alike function to format it like "%u %s" and it will go bang...

Well, for old static binaries, the old syscall ABI would still have to
use 32-bit off_t's and time_t's.  And for dynamically linked binaries,
glibc could deal with the compatibility issues with the old ABI,
across the shared library interface, right?

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