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: <162266000535.3595232.17293899929853400709.b4-ty@chromium.org>
Date:   Wed,  2 Jun 2021 11:53:28 -0700
From:   Kees Cook <keescook@...omium.org>
To:     linux-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>,
        linux-arm-kernel@...ts.infradead.org
Cc:     Kees Cook <keescook@...omium.org>,
        Nathan Chancellor <nathan@...nel.org>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Sami Tolvanen <samitolvanen@...gle.com>
Subject: Re: [PATCH] CFI: Move function_nocfi() into compiler.h

On Wed, 2 Jun 2021 16:37:01 +0100, Mark Rutland wrote:
> Currently the common definition of function_nocfi() is provided by
> <linux/mm.h>, and architectures are expected to provide a definition in
> <asm/memory.h>. Due to header dependencies, this can make it hard to use
> function_nocfi() in low-level headers.
> 
> As function_nocfi() has no dependency on any mm code, nor on any memory
> definitions, it doesn't need to live in <linux/mm.h> or <asm/memory.h>.
> Generally, it would make more sense for it to live in
> <linux/compiler.h>, where an architecture can override it in
> <asm/compiler.h>.
> 
> [...]

Applied to for-next/clang/features, thanks!

[1/1] CFI: Move function_nocfi() into compiler.h
      https://git.kernel.org/kees/c/2d35ea27e0df

-- 
Kees Cook

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ