linux-kernel - Re: [PATCH v2] crypto: arm64/poly1305

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9ca7dcfd-3eb3-4660-b7e8-3f1be94ed3f5@leemhuis.info>
Date: Mon, 12 Aug 2024 08:34:36 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Daniel Gomez <da.gomez@...sung.com>, Jia He <justin.he@....com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
 Andy Polyakov <appro@...ptogams.org>, "David S. Miller"
 <davem@...emloft.net>, Catalin Marinas <catalin.marinas@....com>,
 Will Deacon <will@...nel.org>,
 "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] crypto: arm64/poly1305 - move data to rodata section

On 08.08.24 13:38, Thorsten Leemhuis wrote:
> On 06.08.24 14:55, Daniel Gomez wrote:
>> On Tue, Aug 06, 2024 at 05:54:44AM GMT, Jia He wrote:
>>> When objtool gains support for ARM in the future, it may encounter issues
>>> disassembling the following data in the .text section:
>>>> .Lzeros:
>>>> .long   0,0,0,0,0,0,0,0
>>>> .asciz  "Poly1305 for ARMv8, CRYPTOGAMS by \@dot-asm"
>>>> .align  2
>> [...]
>>
>> I'm getting the following error with next-20240806
>>
>> make LLVM=1 ARCH=arm64 allyesconfig
>> make LLVM=1 ARCH=arm64 -j$(nproc)
>>
>> ld.lld: error: vmlinux.a(arch/arm64/crypto/poly1305-core.o):(function poly1305_blocks_neon: .text+0x3d4): relocation R_AARCH64_ADR_PREL_LO21 out of range: 269166444 is not in [-1048576, 1048575]
> 
> Hmmm, I ran into build problems with -next today for arm64 and x86-64

Turned out my problem was caused by a different change:
https://lore.kernel.org/all/99ae0d34-ed76-4ca0-a9fd-c337da33c9f9@leemhuis.info/

Sorry for the noise.

Ciao, Thorsten