[Devel] [PATCH 0/2] criu: Make sure we don't hit guard page when looking for syscall-ip
Cyrill Gorcunov
gorcunov at gmail.com
Thu Nov 24 07:48:15 PST 2016
When we collect VMAs we may adjust thier start address if
guard page is present and in such case when looking up for
syscall_ip we may choose this guard page address instead of
allowed one so when we call for parasite code injection the
kernel won't allow us to poke syscall code in. Fix it by
testing for guard page in find_syscall_ip.
Note in current vanilla's @criu-dev this won't be a problem
because compel doesn't account guard page when setting up
syscall_ip (but our current master vanilla branch is valuable).
Cyrill Gorcunov (2):
criu: proc_parse -- Add guard page the same way as kernel detects them
parasite: Don't try to start executing syscall from guard page
criu/include/vma.h | 12 ++++++++++++
criu/parasite-syscall.c | 39 ++++++++++++++++++++++-----------------
criu/proc_parse.c | 20 ++++++++++++--------
3 files changed, 46 insertions(+), 25 deletions(-)
--
2.7.4
More information about the Devel
mailing list