linux-kernel - Re: [PATCH] x86/platform/uv: make const pointer dots a static const array

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: <YaZ8vtajDKUVDCne@swahl-home.5wahls.com>
Date:   Tue, 30 Nov 2021 13:34:22 -0600
From:   Steve Wahl <steve.wahl@....com>
To:     Colin Ian King <colin.i.king@...glemail.com>
Cc:     Steve Wahl <steve.wahl@....com>, Mike Travis <mike.travis@....com>,
        Dimitri Sivanich <dimitri.sivanich@....com>,
        Russ Anderson <russ.anderson@....com>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H . Peter Anvin" <hpa@...or.com>,
        platform-driver-x86@...r.kernel.org,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/platform/uv: make const pointer dots a static const
 array

On Sat, Nov 27, 2021 at 05:03:20PM +0000, Colin Ian King wrote:
> Don't populate the const array dots on the stack

That is a misunderstanding of what the original code does.  The
original code has a constant char array (string constant) that is
placed in an initialized data section of memory, the address off which
would be assigned to the pointer "dots" on the stack -- to be clear,
stack contents would not be a full array, but a pointer to it.  Then
that pointer would be passed to the pr_info function (which boils down
to a call to printk).

Examination of the disassembly shows that the compiler actually
eliminates the creation of the pointer "dots" on the stack and just
passes the address of the string constant to the printk function.

So this change should not have any actual effect (I don't know where
you got the "shrinks object code" from), and in my humble opinion
makes the code less clear.

As such, unless there's something here I don't understand, I vote to
reject this patch.

--> Steve Wahl <steve.wahl@....com>

> but make it static
> const and make the pointer an array to remove a dereference. Shrinks
> object code a few bytes too.
> 
> Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> ---
>  arch/x86/platform/uv/uv_nmi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/platform/uv/uv_nmi.c b/arch/x86/platform/uv/uv_nmi.c
> index 1e9ff28bc2e0..2c69a0c30632 100644
> --- a/arch/x86/platform/uv/uv_nmi.c
> +++ b/arch/x86/platform/uv/uv_nmi.c
> @@ -725,7 +725,7 @@ static void uv_nmi_dump_cpu_ip(int cpu, struct pt_regs *regs)
>   */
>  static void uv_nmi_dump_state_cpu(int cpu, struct pt_regs *regs)
>  {
> -	const char *dots = " ................................. ";
> +	static const char dots[] = " ................................. ";
>  
>  	if (cpu == 0)
>  		uv_nmi_dump_cpu_ip_hdr();
> -- 
> 2.33.1
> 

-- 
Steve Wahl, Hewlett Packard Enterprise