> 1) somebody should write registers before final jump to userspace. > Task itself can't generally do it: struct pt_regs is in the same place > as kernel stack. > > cr_load_cpu_regs() does exactly this: as current writes to it's own > pt_regs. Oren, why don't you see crashes? > > I first tried to do it and was greeted with horrible crashes because > e.g current becoming NULL under current. That's why > cr_arch_restore_task_struct() is not done in current context. Hmm, this must an artefact of kernel_thread() approach. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
