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: <250de8f97efe2458afc39f080c3ef6a55f42623c.camel@kernel.org>
Date:   Tue, 07 Sep 2021 18:08:31 +0300
From:   Jarkko Sakkinen <jarkko@...nel.org>
To:     "Luck, Tony" <tony.luck@...el.com>,
        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

On Tue, 2021-09-07 at 15:03 +0000, Luck, Tony wrote:
> > > If I just #include <asm/sgx.h> in those files I'll break the build for other
> > > architectures.
> > 
> > What does specifically break the build?
> 
> There is no file named arch/arm/include/asm/sgx.h (ditto for other architectures that build memory-failure.c and einj.c).
> 
> -Tony

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

/Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ