linux-kernel - Re: [PATCH v4 00/24] ILP32 for ARM64

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: <20150414133810.GC14546@e104818-lin.cambridge.arm.com>
Date:	Tue, 14 Apr 2015 14:38:10 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	"Pinski, Andrew" <Andrew.Pinski@...iumnetworks.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Andreas Kraschitzer <andreas.kraschitzer@...obroma-systems.com>,
	Benedikt Huber <benedikt.huber@...obroma-systems.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Pinski <apinski@...ium.com>,
	Kumar Sankaran <ksankaran@....com>,
	"Dr. Philipp Tomsich" <philipp.tomsich@...obroma-systems.com>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Christoph Muellner <christoph.muellner@...obroma-systems.com>
Subject: Re: [PATCH v4 00/24] ILP32 for ARM64

On Tue, Apr 14, 2015 at 10:45:43AM +0000, Pinski, Andrew wrote:
> Also about time_t, my original patch had used 32bit but was asked to
> change it to the 64bit one. So now I am upset this being asked again
> to change it back.

At the time, we were not aware of plans to fix existing 32-bit
architectures, so we followed Linus' similar request on x32.

> The review process for the linux kernel is much harder than the review
> process of gcc or even glibc now. 

This is not really about kernel code review but about defining the
user/kernel ABI. It shouldn't even be a kernel-only decision, we need to
get the libc people involved. So yes, you get to prototype such ABI in
several kernel patch incarnations and code may be thrown away but that's
better than making the wrong decision on the long run.

As for gcc, the ILP32 ABI is clear to them, they only have to review
implementation details.

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