[CRIU] [PATCH v3 0/2] mem: Address dropped guard pages from procfs report
Adrian Reber
adrian at lisas.de
Thu Jun 29 13:27:21 MSK 2017
On Tue, Jun 27, 2017 at 11:41:06AM -0700, Andrey Vagin wrote:
> Applied
> On Mon, Jun 26, 2017 at 11:55:27PM +0300, Cyrill Gorcunov wrote:
> > Cyrill Gorcunov (2):
> > kerndat: Detect if we have guard page mangle in procfs output
> > mem: Don't assume guard page is returned in procfs with new kernels
> >
> > criu/include/kerndat.h | 1 +
> > criu/include/mem.h | 2 ++
> > criu/kerndat.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++
> > criu/mem.c | 19 +++++++++----
> > criu/proc_parse.c | 3 +-
> > 5 files changed, 95 insertions(+), 6 deletions(-)
> >
> > --
> > 2.7.5
Trying the master branch this fix seems to work on my test system, but
it still fails using the criu-dev branch. I see that these patches exist
on the criu-dev branch but zdtm fails with:
------------------------ grep Error ------------------------
task_args->nr_threads: 1
task_args->clone_restore_fn: 0x11200
task_args->thread_args: 0x22600
(00.006597)pie: 24: Switched to the restorer 24
(00.006598)pie: 24: Error (criu/pie/parasite-vdso.c:49): vdso: BUG at criu/pi>
(00.006598)pie: 24: e/parasite-vdso.c:49
(00.006598)pie: 24: e/parasite-vdso.c:49
(00.009079) Error (criu/cr-restore.c:1472): 24 killed by signal 11: Segmentation fault
(00.009094) Error (criu/cr-restore.c:2378): Restoring FAILED.
------------------------ ERROR OVER ------------------------
Any ideas what I might be doing wrong?
Adrian
More information about the CRIU
mailing list