linux-kernel - Re: [PATCH] kselftest/arm64: bti: force static linking

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: <165272667337.3711461.11956194541511506230.b4-ty@arm.com>
Date:   Mon, 16 May 2022 19:45:11 +0100
From:   Catalin Marinas <catalin.marinas@....com>
To:     Shuah Khan <shuah@...nel.org>, Will Deacon <will@...nel.org>,
        Andre Przywara <andre.przywara@....com>
Cc:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
        linux-kselftest@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] kselftest/arm64: bti: force static linking

On Wed, 11 May 2022 18:21:29 +0100, Andre Przywara wrote:
> The "bti" selftests are built with -nostdlib, which apparently
> automatically creates a statically linked binary, which is what we want
> and need for BTI (to avoid interactions with the dynamic linker).
> 
> However this is not true when building a PIE binary, which some
> toolchains (Ubuntu) configure as the default.
> When compiling btitest with such a toolchain, it will create a
> dynamically linked binary, which will probably fail some tests, as the
> dynamic linker might not support BTI:
> ===================
> TAP version 13
> 1..18
> not ok 1 nohint_func/call_using_br_x0
> not ok 2 nohint_func/call_using_br_x16
> not ok 3 nohint_func/call_using_blr
> ....
> ===================
> 
> [...]

Applied to arm64 (for-next/kselftest), thanks!

[1/1] kselftest/arm64: bti: force static linking
      https://git.kernel.org/arm64/c/d7a49291d786

-- 
Catalin