linux-kernel - RE: [PATCH v4 5/6] x86/sgx: Hook sgx_memory

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: <e0280b82cf964a0797293b0c8e302777@intel.com>
Date:   Tue, 7 Sep 2021 17:46:53 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Jarkko Sakkinen <jarkko@...nel.org>,
        Sean Christopherson <seanjc@...gle.com>,
        "Hansen, Dave" <dave.hansen@...el.com>
CC:     "Zhang, Cathy" <cathy.zhang@...el.com>,
        "x86@...nel.org" <x86@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v4 5/6] x86/sgx: Hook sgx_memory_failure() into mainline
 code

> Would it be too obnoxious to flag that include in those files?

Jarkko,

You mean:

#ifdef CONFIG_X86_SGX
#include <asm/sgx.h>
#endif

in mm/memory-failure.h?

That wouldn't help. I need the do-nothing stub definition on other architectures.

I'm going to explore Dave's suggestion of changing the names to something less sgx specific.

-Tony