linux-kernel - Re: [PATCH] kselftest/arm64: Limit the maximum VL we try to set via ptrace

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] [day] [month] [year] [list]

Message-Id: <167518250322.582901.15647652127648162465.b4-ty@arm.com>
Date:   Tue, 31 Jan 2023 16:28:25 +0000
From:   Catalin Marinas <catalin.marinas@....com>
To:     Will Deacon <will@...nel.org>, Shuah Khan <shuah@...nel.org>,
        Mark Brown <broonie@...nel.org>
Cc:     linux-arm-kernel@...ts.infradead.org,
        linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Limit the maximum VL we try to set via ptrace

On Wed, 11 Jan 2023 15:02:41 +0000, Mark Brown wrote:
> When SVE was initially merged we chose to export the maximum VQ in the ABI
> as being 512, rather more than the architecturally supported maximum of 16.
> For the ptrace tests this results in us generating a lot of test cases and
> hence log output which are redundant since a system couldn't possibly
> support them. Instead only check values up to the current architectural
> limit, plus one more so that we're covering the constraining of higher
> vector lengths.
> 
> [...]

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

[1/1] kselftest/arm64: Limit the maximum VL we try to set via ptrace
      https://git.kernel.org/arm64/c/89ff30b9b720

-- 
Catalin