linux-kernel - Re: [PATCH] x86/mm: Fix warning on build with X86_MEM

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: <e58354f2-d978-2449-67cb-cae63d2b6dd7@google.com>
Date:   Wed, 26 Jan 2022 10:57:12 -0800 (PST)
From:   David Rientjes <rientjes@...gle.com>
To:     "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
cc:     tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
        dave.hansen@...ux.intel.com, x86@...nel.org,
        thomas.lendacky@....com, lkp@...el.com, ak@...ux.intel.com,
        kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        sathyanarayanan.kuppuswamy@...ux.intel.com, tony.luck@...el.com
Subject: Re: [PATCH] x86/mm: Fix warning on build with X86_MEM_ENCRYPT=y

On Wed, 26 Jan 2022, Kirill A. Shutemov wrote:

> So far, AMD_MEM_ENCRYPT is the only user of X86_MEM_ENCRYPT. TDX will be
> the second. It will make mem_encrypt.c build without AMD_MEM_ENCRYPT,
> which triggers a warning:
> 
> arch/x86/mm/mem_encrypt.c:69:13: warning: no previous prototype for
> 	function 'mem_encrypt_init' [-Wmissing-prototypes]
> 
> Fix it by moving mem_encrypt_init() declaration outside of #ifdef
> CONFIG_AMD_MEM_ENCRYPT.
> 
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
> Fixes: 20f07a044a76 ("x86/sev: Move common memory encryption code to mem_encrypt.c")

Acked-by: David Rientjes <rientjes@...gle.com>