From: Ingo Molnar <mingo@kernel.org>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
David Keitel <dkeitel@codeaurora.org>,
Alexander Potapenko <glider@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Vyukov <dvyukov@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alexey Klimov <klimov.linux@gmail.com>,
Yury <yury.norov@gmail.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2] x86/KASAN updates for 4.3
Date: Thu, 13 Aug 2015 08:50:41 +0200 [thread overview]
Message-ID: <20150813065040.GA17983@gmail.com> (raw)
In-Reply-To: <1439444244-26057-1-git-send-email-ryabinin.a.a@gmail.com>
* Andrey Ryabinin <ryabinin.a.a@gmail.com> wrote:
> These 2 patches taken from v5 'KASAN for arm64' series.
> The only change is updated changelog in second patch.
>
> I hope this is not too late to queue these for 4.3,
> as this allow us to merge arm64/KASAN patches in v4.4
> through arm64 tree.
>
> Andrey Ryabinin (2):
> x86/kasan: define KASAN_SHADOW_OFFSET per architecture
> x86/kasan, mm: introduce generic kasan_populate_zero_shadow()
>
> arch/x86/include/asm/kasan.h | 3 +
> arch/x86/mm/kasan_init_64.c | 123 ++--------------------------------
> include/linux/kasan.h | 10 ++-
> mm/kasan/Makefile | 2 +-
> mm/kasan/kasan_init.c | 152 +++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 170 insertions(+), 120 deletions(-)
> create mode 100644 mm/kasan/kasan_init.c
It's absolutely too late in the -rc cycle for v4.3!
I can create a stable topic tree for it, tip:mm/kasan or so, which arm64 could
pull and base its own ARM specific work on, if that's OK with everyone.
Thanks,
Ingo
next prev parent reply other threads:[~2015-08-13 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 5:37 [PATCH 0/2] x86/KASAN updates for 4.3 Andrey Ryabinin
2015-08-13 5:37 ` [PATCH v6 1/2] x86/kasan: define KASAN_SHADOW_OFFSET per architecture Andrey Ryabinin
2015-08-22 13:59 ` [tip:mm/kasan] x86/kasan: Define " tip-bot for Andrey Ryabinin
2015-08-13 5:37 ` [PATCH v6 2/2] x86/kasan, mm: introduce generic kasan_populate_zero_shadow() Andrey Ryabinin
2015-08-22 13:59 ` [tip:mm/kasan] x86/kasan, mm: Introduce " tip-bot for Andrey Ryabinin
2015-08-13 6:50 ` Ingo Molnar [this message]
2015-08-13 8:16 ` [PATCH 0/2] x86/KASAN updates for 4.3 Ingo Molnar
2015-08-13 9:01 ` Will Deacon
2015-08-13 11:02 ` Andrey Ryabinin
2015-08-13 11:24 ` Will Deacon
2015-08-13 17:23 ` Will Deacon
2015-08-22 10:09 ` Ingo Molnar
2015-08-22 12:51 ` Andrey Ryabinin
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=20150813065040.GA17983@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dkeitel@codeaurora.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=klimov.linux@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.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).