linux-kernel - Re: [PATCH] selftests/arm64: Prevent build warnings from -Wmaybe-uninitialized

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: <dd3dee5a-b030-4658-8cef-c777928368d4@sirena.org.uk>
Date: Wed, 25 Jun 2025 11:24:30 +0100
From: Mark Brown <broonie@...nel.org>
To: Anshuman Khandual <anshuman.khandual@....com>
Cc: linux-arm-kernel@...ts.infradead.org,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will@...nel.org>, Shuah Khan <shuah@...nel.org>,
	linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] selftests/arm64: Prevent build warnings from
 -Wmaybe-uninitialized

On Wed, Jun 25, 2025 at 03:01:38AM +0100, Anshuman Khandual wrote:

> @@ -96,7 +96,7 @@ static int write_sleep_read(void)
>  static int write_fork_read(void)
>  {
>  	pid_t newpid, waiting, oldpid;
> -	int status;
> +	int status = 0;
>  
>  	set_tpidr2(getpid());
>  

This will shut the warnings up, but it's a bit of a heavy hammer that
means that the warning can never trigger warnings for that variable
being unused.  Is it possible to fix this by updating the control flow
such that the compiler can tell that the initialisation follows the use?

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