Commit cab42bca authored by Cyrill Gorcunov's avatar Cyrill Gorcunov Committed by Pavel Emelyanov

x86: sigframe -- Don't forget to copy ss

Make sure we don't pass any trash value here, because
the kernel does copy it explicitly. We allocate the
memory for frame as zero filled but stack segment
is special and zero is not acceptable (we've had
a discussion on LKML if we need a special handling
for zero ss but end up that new kernels need new CRIU
version, upon which all agreed). Finally in
commit 296bbf7e I managed to hit exactly
this problem :)
Reported-by: 's avatarAndrey Wagin <avagin@gmail.com>
Signed-off-by: 's avatarCyrill Gorcunov <gorcunov@openvz.org>
Acked-by: 's avatarAndrey Wagin <avagin@gmail.com>
Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
parent 3e0b09b1
...@@ -486,10 +486,7 @@ int restore_gpregs(struct rt_sigframe *f, UserX86RegsEntry *r) ...@@ -486,10 +486,7 @@ int restore_gpregs(struct rt_sigframe *f, UserX86RegsEntry *r)
CPREG2(eflags, flags); CPREG2(eflags, flags);
CPREG1(cs); CPREG1(cs);
#ifdef CONFIG_X86_32
CPREG1(ss); CPREG1(ss);
#endif
#ifdef CONFIG_X86_32 #ifdef CONFIG_X86_32
CPREG1(gs); CPREG1(gs);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment