[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180104183504.GQ28752@n2100.armlinux.org.uk>
Date: Thu, 4 Jan 2018 18:35:04 +0000
From: Russell King - ARM Linux <linux@...linux.org.uk>
To: Kees Cook <keescook@...omium.org>
Cc: Jinbum Park <jinb.park7@...il.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
kernel-hardening@...ts.openwall.com,
Will Deacon <will.deacon@....com>,
LKML <linux-kernel@...r.kernel.org>,
Dave Martin <Dave.Martin@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [kernel-hardening] [PATCH] arm: Always use REFCOUNT_FULL
On Thu, Jan 04, 2018 at 10:32:46AM -0800, Kees Cook wrote:
> On Thu, Jan 4, 2018 at 4:28 AM, Jinbum Park <jinb.park7@...il.com> wrote:
> > arm prefers to use REFCOUNT_FULL by default.
> > This enables it for arm.
> >
> > Signed-off-by: Jinbum Park <jinb.park7@...il.com>
>
> Acked-by: Kees Cook <keescook@...omium.org>
I'd help if there was some kind of explanation about this. Not
everyone knows what REFCOUNT_FULL is.
Also, why does "arm" "prefer" to use this? Where does the preference
come from - and why is it a preference but being enforced by the
Kconfig ?
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
Powered by blists - more mailing lists