[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171103185147.2688-1-pasha.tatashin@oracle.com>
Date: Fri, 3 Nov 2017 14:51:45 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: aryabinin@...tuozzo.com, will.deacon@....com, mhocko@...nel.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-arm-kernel@...ts.infradead.org,
x86@...nel.org, kasan-dev@...glegroups.com, borntraeger@...ibm.com,
heiko.carstens@...ibm.com, willy@...radead.org,
ard.biesheuvel@...aro.org, mark.rutland@....com,
catalin.marinas@....com, sam@...nborg.org,
mgorman@...hsingularity.net, steven.sistare@...cle.com,
daniel.m.jordan@...cle.com, bob.picco@...cle.com
Subject: [PATCH v1 0/2] don't use vmemmap_populate() to initialize shadow
Andrey Ryabinin asked to replace the three patches in my series:
x86-kasan-add-and-use-kasan_map_populate.patch
arm64-kasan-add-and-use-kasan_map_populate.patch
arm64-kasan-avoid-using-vmemmap_populate-to-initialise-shadow.patch
With two patches in this thread:
x86/mm/kasan: don't use vmemmap_populate() to initialize shadow
arm64/mm/kasan: don't use vmemmap_populate() to initialize shadow
Pavel Tatashin (2):
x86/mm/kasan: don't use vmemmap_populate() to initialize shadow
arm64/mm/kasan: don't use vmemmap_populate() to initialize shadow
arch/arm64/Kconfig | 2 +-
arch/arm64/mm/kasan_init.c | 130 ++++++++++++++++++++++++----------------
arch/x86/Kconfig | 2 +-
arch/x86/mm/kasan_init_64.c | 143 +++++++++++++++++++++++++++++++++++++++++---
4 files changed, 218 insertions(+), 59 deletions(-)
--
2.15.0
Powered by blists - more mailing lists