[CRIU] [PATCH 4/7] dump: Do save thread blocked signals in a parasite memory
Cyrill Gorcunov
gorcunov at openvz.org
Sun Nov 4 15:06:51 EST 2012
Once we seized the thread we need to save a copy of blocked
signals in parasite memory, just like it's done for a thread
leader task.
This patch does exactly that -- we call for parasite_init_threads_seized
helper which tells parasite to save blocked signal mask, then
we fetch the data specific to thread with parasite_dump_thread_seized.
Note since it's not longer just @tid and @tid_addr fetched from the
parasite, I've renamed PARASITE_CMD_DUMP_TID_ADDR to
PARASITE_CMD_DUMP_THREAD, because it's already too many characteristics
we're fetching and likely it'll be extened even more in future.
Use parasite_init_threads_seized helper which walks over
all threads (except a leader, which already saved at infection
time) and saves blocked signals mask in parasite memory.
Signed-off-by: Cyrill Gorcunov <gorcunov at openvz.org>
---
cr-dump.c | 16 +++++++++++++---
include/parasite-syscall.h | 8 ++++++--
include/parasite.h | 8 +++++---
parasite-syscall.c | 33 +++++++++++++++++++++++++++++----
parasite.c | 31 ++++++++++++++++++++++++++++---
5 files changed, 81 insertions(+), 15 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-dump-Do-save-thread-blocked-signals-in-a-parasite-me.patch
Type: text/x-patch
Size: 5891 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20121105/849bb617/attachment.bin>
More information about the CRIU
mailing list