The problem can occur with any application as stated by Boris Ostrovsky
------------
"This can be easily triggered by Linux' page-types
(tools/vm/page-types.c) after save/restore.
All it does is it walks the page tables (in fs/proc/task_mmu.c) and
eventually trips on bad page. For example:
# /page-types -p 2273 -L> /tmp/new
[ 2634.501440] pfn 0x159f75 highest_memmap_pfn=0x3ffff
[ 2634.502345] BUG: Bad page map in process page-types pte:159f75420
pmd:3178a067
"
Which means that any application should be able to trigger this depending
on whether 'mprotect' was doing its stuff and migration happend.
The problem can occur with any application as stated by Boris Ostrovsky
------------ vm/page- types.c) after save/restore.
"This can be easily triggered by Linux' page-types
(tools/
All it does is it walks the page tables (in fs/proc/task_mmu.c) and
eventually trips on bad page. For example:
# /page-types -p 2273 -L> /tmp/new memmap_ pfn=0x3ffff
[ 2634.501440] pfn 0x159f75 highest_
[ 2634.502345] BUG: Bad page map in process page-types pte:159f75420
pmd:3178a067
"
Which means that any application should be able to trigger this depending
on whether 'mprotect' was doing its stuff and migration happend.
Please note that these guests have no NUMA information exposed at all. www.gossamer- threads. com/lists/ xen/devel/ 322227? page=last ]------
------[Ref: http://