linux-kernel - Re: [PATCH] kselftest/arm64: Check that SVCR is 0 in signal handlers

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: <ZzNXQtbk1NWN6F7f@finisterre.sirena.org.uk>
Date: Tue, 12 Nov 2024 13:25:22 +0000
From: Mark Brown <broonie@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Will Deacon <will@...nel.org>, Shuah Khan <shuah@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Check that SVCR is 0 in signal handlers

On Tue, Nov 12, 2024 at 11:30:14AM +0000, Catalin Marinas wrote:
> On Wed, Nov 06, 2024 at 05:07:51PM +0000, Mark Brown wrote:

> > +		fprintf(stderr, "Unexpected SVCR %llx\n", get_svcr());
> > +		return 1;
> > +	}

> I think I'll change both printf specifiers to %lx here since in the libc
> I have installed, uin64_t is an unsigned long (the kernel defines it as
> unsigned long long). Both gcc and clang complain but the compiler
> shouldn't matter since the headers come with glibc.

Makes sense.  I do wish the compilers were more consistent with
including these warnings :(

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)