[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 3 Mar 2016 16:11:52 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Mark Rutland <mark.rutland@....com>
Cc: Ingo Molnar <mingo@...nel.org>, akpm@...ux-foundation.org,
aryabinin@...tuozzo.com, linux-arch@...r.kernel.org,
lorenzo.pieralisi@....com, peterz@...radead.org,
will.deacon@....com, linux-kernel@...r.kernel.org,
mingo@...hat.com, glider@...gle.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] KASAN: clean stale poison upon cold re-entry to
kernel
On Thu, Mar 03, 2016 at 12:38:09PM +0000, Mark Rutland wrote:
> On Thu, Mar 03, 2016 at 01:02:27PM +0100, Ingo Molnar wrote:
> > Mark Rutland <mark.rutland@....com> wrote:
> > > Mark Rutland (3):
> > > kasan: add functions to clear stack poison
> > > sched/kasan: remove stale KASAN poison after hotplug
> > > arm64: kasan: clear stale stack poison
> > >
> > > arch/arm64/kernel/sleep.S | 4 ++++
> > > include/linux/kasan.h | 6 +++++-
> > > kernel/sched/core.c | 3 +++
> > > mm/kasan/kasan.c | 20 ++++++++++++++++++++
> > > 4 files changed, 32 insertions(+), 1 deletion(-)
> >
> > Looks good to me - via which tree would you like to see this merged upstream?
>
> I'd prefer the arm64 tree as arm64 is (the most) affected by the issue
> in practice.
>
> I'm happy for this to go via another tree if that's simpler; I'm not
> aware of anything that's likely to conflict in the arm64 tree.
>
> Catalin, Andrey, Andrew, any preference?
I'm happy for this to go via the Andrew's -mm tree. For the series:
Acked-by: Catalin Marinas <catalin.marinas@....com>
Please report the series to linux-mm@...ck.org with the corresponding
acks in place and the fix-up on patch 1.
Thanks.
--
Catalin
Powered by blists - more mailing lists