linux-kernel - Re: 64-syscall args on 32-bit vs syscall()

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: <20100319012232.GA14108@shareable.org>
Date:	Fri, 19 Mar 2010 01:22:33 +0000
From:	Jamie Lokier <jamie@...reable.org>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	munroesj@...ibm.com, Andreas Schwab <schwab@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Ulrich Drepper <drepper@...hat.com>,
	David Miller <davem@...emloft.net>, ralf@...ux-mips.org,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel@...savvy.com, torvalds@...ux-foundation.org
Subject: Re: 64-syscall args on 32-bit vs syscall()

Benjamin Herrenschmidt wrote:
> On Thu, 2010-03-18 at 12:03 -0500, Steven Munroe wrote:
> > Sorry in and long are compatible in 32-bit but not long long.
> > 
> > int and long are not compatible in 64-bit
> > 
> > It is hard the keep all the nodes and arguments straight.
> > 
> > But the concern about changing the prototype and are people actually
> > using the prototype are still valid.
> 
> Well, using the macro trick instead would fix that problem, code
> wouldn't build if it doesn't include unistd.h :-)

Or it will build, but call the old ABI version - no change to those programs.

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