linux-kernel - Re: [PATCH] regulator: Make constraint debug processing conditional on DEBUG

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]

Date:   Mon, 05 Oct 2020 18:54:28 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Make constraint debug processing conditional on DEBUG

On Mon, 5 Oct 2020 15:15:46 +0200, Geert Uytterhoeven wrote:
> If debugging is disabled, print_constraints() does not print the actual
> constraints, but still performs some processing and string formatting,
> only to throw away the result later.
> 
> Fix this by moving all constraint debug processing to a separate
> function, and replacing it by a dummy when debugging is disabled.
> This reduces kernel size by almost 800 bytes (on arm/arm64).

Applied to

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

Thanks!

[1/1] regulator: Make constraint debug processing conditional on DEBUG
      commit: c845f21ad86528f888db27849f2d315e08126816

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