linux-kernel - Re: [PATCH] regmap: maple: work around gcc-14.1 false-positive warning

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: <172167370279.77740.16466974603431770496.b4-ty@kernel.org>
Date: Mon, 22 Jul 2024 19:41:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 Arnd Bergmann <arnd@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, "Rafael J. Wysocki" <rafael@...nel.org>, 
 Richard Fitzgerald <rf@...nsource.cirrus.com>, 
 Guenter Roeck <linux@...ck-us.net>, Colin Ian King <colin.i.king@...il.com>, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: maple: work around gcc-14.1 false-positive
 warning

On Fri, 19 Jul 2024 12:40:24 +0200, Arnd Bergmann wrote:
> With gcc-14.1, there is a false-postive -Wuninitialized warning in
> regcache_maple_drop:
> 
> drivers/base/regmap/regcache-maple.c: In function 'regcache_maple_drop':
> drivers/base/regmap/regcache-maple.c:113:23: error: 'lower_index' is used uninitialized [-Werror=uninitialized]
>   113 |         unsigned long lower_index, lower_last;
>       |                       ^~~~~~~~~~~
> drivers/base/regmap/regcache-maple.c:113:36: error: 'lower_last' is used uninitialized [-Werror=uninitialized]
>   113 |         unsigned long lower_index, lower_last;
>       |                                    ^~~~~~~~~~
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: maple: work around gcc-14.1 false-positive warning
      commit: 542440fd7b30983cae23e32bd22f69a076ec7ef4

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark