[CRIU] [PATCH 0/2] dump: Add more information about objects we processing

Cyrill Gorcunov gorcunov at openvz.org
Thu Jun 30 12:04:43 PDT 2016


Hi guys, I found that in case if container get killed (or say here are
several attempts to dump container, where first one fails but second
successes) the logs may be not that informative:

 - in particular when problem happens on dumping external files and
   we're failing, the only information we get on hands is file descriptor
   number. Lets at least show the object /proc/pid/fd/N points to.

 - when dumping processes and error happens -- we only have process
   PID printed, lets show process comm at least.

   I'm not sure in this patch though -- maybe it worth showing process'
   comm during seize procedure as well?

Commenst are welcome -- the best log is that when we don't need images
or container to run after failure. Lets move more information into the
log engine.

Cyrill Gorcunov (2):
  dump: Show task comm early
  dump: files-ext -- Show exactly which file can't be dumped

 criu/cr-dump.c | 41 ++++++++++++++++++++++++++++++++++++++---
 criu/files.c   | 13 ++++++++++---
 2 files changed, 48 insertions(+), 6 deletions(-)

-- 
2.7.4



More information about the CRIU mailing list