On 20 September 2017 at 13:49, Kees Cook <keesc...@chromium.org> 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.biesheu...@linaro.org> > Cc: hw.li...@huawei.com > Cc: Catalin Marinas <catalin.mari...@arm.com> > Cc: Will Deacon <will.dea...@arm.com> > Cc: linux-arm-ker...@lists.infradead.org > Signed-off-by: Kees Cook <keesc...@chromium.org>
Acked-by: Ard Biesheuvel <ard.biesheu...@linaro.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 > select SPARSE_IRQ > select SYSCTL_EXCEPTION_TRACE > select THREAD_INFO_IN_TASK > -- > 2.7.4 > > > -- > Kees Cook > Pixel Security