From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@kernel.org>,
akpm@linux-foundation.org, catalin.marinas@arm.com
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, glider@google.com,
lorenzo.pieralisi@arm.com, mingo@redhat.com,
peterz@infradead.org, will.deacon@arm.com
Subject: Re: [PATCH 0/3] KASAN: clean stale poison upon cold re-entry to kernel
Date: Thu, 3 Mar 2016 17:30:17 +0300 [thread overview]
Message-ID: <56D84A79.2030303@virtuozzo.com> (raw)
In-Reply-To: <20160303123809.GA19139@leverpostej>
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@virtuozzo.com>
next prev parent reply other threads:[~2016-03-03 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 14:26 [PATCH 0/3] KASAN: clean stale poison upon cold re-entry to kernel Mark Rutland
2016-03-02 14:26 ` [PATCH 1/3] kasan: add functions to clear stack poison Mark Rutland
2016-03-02 14:26 ` Mark Rutland
2016-03-02 14:26 ` [PATCH 2/3] sched/kasan: remove stale KASAN poison after hotplug Mark Rutland
2016-03-02 14:26 ` Mark Rutland
2016-03-02 14:26 ` [PATCH 3/3] arm64: kasan: clear stale stack poison Mark Rutland
2016-03-02 14:26 ` Mark Rutland
2016-03-03 14:14 ` Mark Rutland
2016-03-03 14:32 ` Lorenzo Pieralisi
2016-03-03 14:32 ` Lorenzo Pieralisi
2016-03-03 12:02 ` [PATCH 0/3] KASAN: clean stale poison upon cold re-entry to kernel Ingo Molnar
2016-03-03 12:02 ` Ingo Molnar
2016-03-03 12:38 ` Mark Rutland
2016-03-03 12:44 ` Ingo Molnar
2016-03-03 12:44 ` Ingo Molnar
2016-03-03 14:30 ` Andrey Ryabinin [this message]
2016-03-03 14:49 ` Mark Rutland
2016-03-03 14:49 ` Mark Rutland
2016-03-03 14:53 ` Andrey Ryabinin
2016-03-03 14:53 ` Andrey Ryabinin
2016-03-03 16:11 ` Catalin Marinas
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=56D84A79.2030303@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=glider@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).