linux-kernel - Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

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:	Sat, 25 Jun 2016 16:26:01 -0700
From:	Andrew Pinski <pinskia@...il.com>
To:	Florian Weimer <fweimer@...hat.com>
Cc:	Andreas Schwab <schwab@...e.de>,
	Yury Norov <ynorov@...iumnetworks.com>,
	Szabolcs Nagy <szabolcs.nagy@....com>,
	GNU C Library <libc-alpha@...rceware.org>,
	LKML <linux-kernel@...r.kernel.org>, nd <nd@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Catalin Marinas <catalin.marinas@....com>,
	Marcus Shawcroft <marcus.shawcroft@....com>, philb@....org,
	David Miller <davem@...emloft.net>,
	Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
	"Joseph S. Myers" <joseph@...esourcery.com>,
	Andrew Pinski <apinski@...ium.com>
Subject: Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

On Fri, Jun 24, 2016 at 4:38 AM, Florian Weimer <fweimer@...hat.com> wrote:
> On 06/23/2016 09:56 AM, Andreas Schwab wrote:
>>
>> Andrew Pinski <pinskia@...il.com> writes:
>>
>>> So the question becomes do we care enough about the incompatibles
>>> between AARCH32 and AARCH64 to fix this and go just worry about ILP32
>>> and LP64?
>>
>>
>> Some armv8 chips do not implement all of armv7, so how relevant is
>> aarch32 on aarch64?
>
>
> I also do not see sufficient justification for this ABI break.

Yury,
  Can you patch ILP32 glibc to use 64bit integer for utmp struct?

>
> Thanks,
> Florian
>