From: Al Viro <viro@ZenIV.linux.org.uk>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
hw.likun@huawei.com
Subject: Re: [PATCH] arm64: Always use REFCOUNT_FULL
Date: Thu, 21 Sep 2017 18:45:48 +0100 [thread overview]
Message-ID: <20170921174548.GM32076@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20170920204959.GA79741@beast>
On Wed, Sep 20, 2017 at 01:49:59PM -0700, Kees Cook wrote:
> As discussed at the Linux Security Summit, arm64 prefers to use
> REFCOUNT_FULL by default. This enables it for the architecture.
>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: hw.likun@huawei.com
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> arch/arm64/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 0df64a6a56d4..9fe7a7f4c94c 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -119,6 +119,7 @@ config ARM64
> select PCI_ECAM if ACPI
> select POWER_RESET
> select POWER_SUPPLY
> + select REFCOUNT_FULL
Umm... That does a bit more than "on by default", unless I'm
misreading it. More like "on, and you can't opt out"...
next prev parent reply other threads:[~2017-09-21 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 20:49 [PATCH] arm64: Always use REFCOUNT_FULL Kees Cook
2017-09-20 22:44 ` Ard Biesheuvel
2017-09-21 17:45 ` Al Viro [this message]
2017-09-21 17:52 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170921174548.GM32076@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=hw.likun@huawei.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox