Re: [PATCH 0/7][v8] Container-init signal semantics

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2009-03-07 at 20:43 +0100, Daniel Lezcano wrote:
>         case LINUX_REBOOT_CMD_HALT:
> -               kernel_halt();
> -               unlock_kernel();
> -               do_exit(0);
> +               if (power_off_pid_ns(current->nsproxy->pid_ns)) {
> +                       kernel_halt();
> +                       unlock_kernel();
> +                       do_exit(0);
> +               }

Even if current will get SIGKILLed when zap_pid_ns_processes() is
called, I see no reason it doesn't call do_exit(0).

>                 break;
> 
>         case LINUX_REBOOT_CMD_POWER_OFF:
> -               kernel_power_off();
> -               unlock_kernel();
> -               do_exit(0);
> +               if (power_off_pid_ns(current->nsproxy->pid_ns)) {
> +                       kernel_power_off();
> +                       unlock_kernel();
> +                       do_exit(0);
> +               }

Same.

>                 break;
> 
-- 
Gregory Kurz                                     gkurz@xxxxxxxxxx
Software Engineer @ IBM/Meiosys                  http://www.ibm.com
Tel +33 (0)534 638 479                           Fax +33 (0)561 400 420

"Anarchy is about taking complete responsibility for yourself."
        Alan Moore.

_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers

[Index of Archives]     [Cgroups]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux