public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@free.fr>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	LXC Development <Lxc-devel@lists.sourceforge.net>,
	containers@lists.linux-foundation.org
Subject: Re: [RFC] catching sys_reboot syscall
Date: Wed, 10 Aug 2011 22:49:39 +0200	[thread overview]
Message-ID: <4E42EEE3.9050608@free.fr> (raw)
In-Reply-To: <20110810221028.2e0c8590@neptune.home>

On 08/10/2011 10:10 PM, Bruno Prémont wrote:
> Hi Daniel,
>
> [I'm adding containers ml as we had a discussion there some time ago
>  for this feature]

[ ... ]

>> +    if (cmd == LINUX_REBOOT_CMD_RESTART2)
>> +        if (strncpy_from_user(&buffer[0], arg, sizeof(buffer) - 1) < 0)
>> +            return -EFAULT;
>> +
>> +    /* If we are not in the initial pid namespace, we send a signal
>> +     * to the parent of this init pid namespace, notifying a shutdown
>> +     * occured */
>> +    if (pid_ns != &init_pid_ns)
>> +        pid_namespace_reboot(pid_ns, cmd, buffer);
> Should there be a return here?
> Or does pid_namespace_reboot() never return by submitting signal to
> parent?

Yes, it does not return a value, like 'do_notify_parent_cldstop'

Thanks
   -- Daniel

  reply	other threads:[~2011-08-10 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 21:14 [RFC] catching sys_reboot syscall Daniel Lezcano
2011-08-10 20:10 ` Bruno Prémont
2011-08-10 20:49   ` Daniel Lezcano [this message]
2011-08-11 16:30     ` Bruno Prémont
2011-08-11 16:49       ` Daniel Lezcano
2011-08-11 17:04         ` Bruno Prémont
2011-08-11 18:10           ` [lxc-devel] " Daniel Lezcano
2011-08-11 18:10           ` Serge Hallyn
2011-08-11 18:40             ` [PATCH] add pid->user_ns Serge Hallyn
2011-08-20 11:03 ` [RFC] catching sys_reboot syscall Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E42EEE3.9050608@free.fr \
    --to=daniel.lezcano@free.fr \
    --cc=Lxc-devel@lists.sourceforge.net \
    --cc=bonbons@linux-vserver.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox