1. Replace these two patches:
arm64/kasan: add and use kasan_map_populate()
x86/kasan: add and use kasan_map_populate()
With:
x86/mm/kasan: don't use vmemmap_populate() to initialize
shadow
arm64/mm/kasan: don't use vmemmap_populate() to initialize
shadow
Pavel, could you please send the
Hi Andrew and Michal,
There are a few changes I need to do to my series:
1. Replace these two patches:
arm64/kasan: add and use kasan_map_populate()
x86/kasan: add and use kasan_map_populate()
With:
x86/mm/kasan: don't use vmemmap_populate() to initialize
shadow
arm64/mm/kasan: don't use vme
As I said, I'm fine either way, I just didn't want to cause extra work
or rebasing:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/535703.html
Makes sense. I am also fine either way, I can submit a new patch merging
together the two if needed.
Pavel
On Wed, Oct 18, 2017 at 01:03:10PM -0400, Pavel Tatashin wrote:
> I asked Will, about it, and he preferred to have this patched added to the
> end of my series instead of replacing "arm64/kasan: add and use
> kasan_map_populate()".
As I said, I'm fine either way, I just didn't want to cause extra
Hi Andrey,
I asked Will, about it, and he preferred to have this patched added to
the end of my series instead of replacing "arm64/kasan: add and use
kasan_map_populate()".
In addition, Will's patch stops using large pages for kasan memory, and
thus might add some regression in which case it
During early boot, kasan uses vmemmap_populate() to establish its shadow
memory. But, that interface is intended for struct pages use.
Because of the current project, vmemmap won't be zeroed during allocation,
but kasan expects that memory to be zeroed. We are adding a new
kasan_map_populate() fun
