Quoting Dave Hansen (dave@xxxxxxxxxxxxxxxxxx): > On Fri, 2008-07-11 at 08:13 -0500, Serge E. Hallyn wrote: > > > > One thing we could do here is to start extending the cryo approach > > with Eric's checkpoint-as-a-coredump (caac?). We generate the > > tiniest of coredumps which, at first, contains nothing but > > mm->arg_start and maybe a process id. It would be simplest if > > it also contained a filename for the real executable, > > The exec model sounds reasonable to me. > > But, I think the filename of the exe is going to have to be in the > checkpoint *already*. It is mapped by at least one of the VMAs, and > will probably be dumped as a normal file-backed area. > > Now, since arg_start is already set up at exec time, it doesn't seem > unreasonable to have the theoretical fs/binfmt_cr.c set it as well. > > -- Dave Ok. So I'll play with this a bit over the next week. I'm mostly unfamiliar with the coredump code and have looked through the binfmts mainly for tracking the order of security events, so this should be fun. -serge _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
