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: <5769139E.7020805@arm.com>
Date:	Tue, 21 Jun 2016 11:14:54 +0100
From:	Szabolcs Nagy <szabolcs.nagy@....com>
To:	Yury Norov <ynorov@...iumnetworks.com>,
	<libc-alpha@...rceware.org>, <linux-kernel@...r.kernel.org>
CC:	<nd@....com>, <arnd@...db.de>, <catalin.marinas@....com>,
	<marcus.shawcroft@....com>, <philb@....org>, <davem@...emloft.net>,
	<maxim.kuvyrkov@...aro.org>, <joseph@...esourcery.com>,
	<pinskia@...il.com>, Andrew Pinski <apinski@...ium.com>
Subject: Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

On 21/06/16 06:06, Yury Norov wrote:
> From: Andrew Pinski <apinski@...ium.com>
> 
> NOTE This is an ABI change for AARCH64.
> If you have some AARCH32 and AARCH64 applications and they both use
> utmp, one of them will fail due to the use of time_t inside the
> utmp binary format.
> 
> This fixes the problem by setting __WORDSIZE_TIME64_COMPAT32.

i think changing the abi now is not ok.

this is BZ 17470 and i think it should be discussed separately
from ilp32.

if it's possible to detect the utmp file format, that would
allow a reasonable fix, the way glibc changes the struct def
based on lp64 targets is non-conforming.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ