[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 3 Mar 2016 17:30:17 +0300
From: Andrey Ryabinin <aryabinin@...tuozzo.com>
To: Mark Rutland <mark.rutland@....com>,
Ingo Molnar <mingo@...nel.org>, <akpm@...ux-foundation.org>,
<catalin.marinas@....com>
CC: <linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <glider@...gle.com>,
<lorenzo.pieralisi@....com>, <mingo@...hat.com>,
<peterz@...radead.org>, <will.deacon@....com>
Subject: Re: [PATCH 0/3] KASAN: clean stale poison upon cold re-entry to
kernel
On 03/03/2016 03:38 PM, Mark Rutland wrote:
> On Thu, Mar 03, 2016 at 01:02:27PM +0100, Ingo Molnar 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 don't have any. arm64 tree is fine by me.
For the patchset:
Reviewed-by: Andrey Ryabinin <aryabinin@...tuozzo.com>
Powered by blists - more mailing lists