All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cedric Le Goater <legoater@free.fr>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Emelianov <xemul@openvz.org>,
	Herbert Poetzl <herbert@13thfloor.at>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	Linux Containers <containers@lists.osdl.org>
Subject: Re: PATCH -mm] fix create_new_namespaces() return value
Date: Tue, 12 Jun 2007 09:49:10 +0200	[thread overview]
Message-ID: <466E4FF6.8040709@free.fr> (raw)
In-Reply-To: <466D76DC.7020900@us.ibm.com>

Badari Pulavarty wrote:
> 
> 
> Cedric Le Goater wrote:
> 
>> The following patch modifies create_new_namespaces() to also use the
>> errors returned by the copy_*_ns routines and not to systematically
>> return ENOMEM.
>>
> 
> In my initial version, I did same. It doesn't work :(
> 
> copy_*_ns() routines doesn't return any errors. All they return is NULL
> in case of a
> failure + with the exception of copy_mnt_ns, there are no other failure
> cases.

mnt ant uts namespaces return NULL right but this is not true for ipc namespace 
which returns -ENOMEM. user namespace returns -EINVAL if CONFIG_USER_NS is not 
selected. I expect pid namespace to do same and net namespace to do even more.

> So, there is no way to find out why the copy_*_ns() routines failed from
> create_new_namespaces().
> If you really really want to do this, change all copy_*_ns() routines to
> returns meaningful errors instead of NULL.

I will certainly do and change mnt ant uts namespaces to return -ENOMEM but
we will still require the patch below.

>> Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
>> Cc: Serge E. Hallyn <serue@us.ibm.com>
>> Cc: Badari Pulavarty <pbadari@us.ibm.com>
>> Cc: Pavel Emelianov <xemul@openvz.org>
>> Cc: Herbert Poetzl <herbert@13thfloor.at>
>> Cc: Eric W. Biederman <ebiederm@xmission.com>
>> ---
>> kernel/nsproxy.c |   23 +++++++++++++++++------
>> 1 file changed, 17 insertions(+), 6 deletions(-)
>>
>> Index: 2.6.22-rc4-mm2/kernel/nsproxy.c
>> ===================================================================
>> --- 2.6.22-rc4-mm2.orig/kernel/nsproxy.c
>> +++ 2.6.22-rc4-mm2/kernel/nsproxy.c
>> @@ -58,30 +58,41 @@ static struct nsproxy *create_new_namesp
>>             struct fs_struct *new_fs)
>> {
>>     struct nsproxy *new_nsp;
>> +    int err;
>>
>>     new_nsp = clone_nsproxy(tsk->nsproxy);
>>     if (!new_nsp)
>>         return ERR_PTR(-ENOMEM);
>>
>>     new_nsp->mnt_ns = copy_mnt_ns(flags, tsk->nsproxy->mnt_ns, new_fs);
>> -    if (IS_ERR(new_nsp->mnt_ns))
>> +    if (IS_ERR(new_nsp->mnt_ns)) {
>> +        err = PTR_ERR(new_nsp->mnt_ns);
>>         goto out_ns;
>> +    }
>>
>>     new_nsp->uts_ns = copy_utsname(flags, tsk->nsproxy->uts_ns);
>> -    if (IS_ERR(new_nsp->uts_ns))
>> +    if (IS_ERR(new_nsp->uts_ns)) {
>> +        err = PTR_ERR(new_nsp->uts_ns);
>>         goto out_uts;
>> +    }
>>
>>     new_nsp->ipc_ns = copy_ipcs(flags, tsk->nsproxy->ipc_ns);
>> -    if (IS_ERR(new_nsp->ipc_ns))
>> +    if (IS_ERR(new_nsp->ipc_ns)) {
>> +        err = PTR_ERR(new_nsp->ipc_ns);
>>         goto out_ipc;
>> +    }
>>
>>     new_nsp->pid_ns = copy_pid_ns(flags, tsk->nsproxy->pid_ns);
>> -    if (IS_ERR(new_nsp->pid_ns))
>> +    if (IS_ERR(new_nsp->pid_ns)) {
>> +        err = PTR_ERR(new_nsp->pid_ns);
>>         goto out_pid;
>> +    }
>>
>>     new_nsp->user_ns = copy_user_ns(flags, tsk->nsproxy->user_ns);
>> -    if (IS_ERR(new_nsp->user_ns))
>> +    if (IS_ERR(new_nsp->user_ns)) {
>> +        err = PTR_ERR(new_nsp->user_ns);
>>
> Hmm.. copy_user_ns() ? I don't see this in rc4-mm2.

it's in the -mm stack.

C. 

  reply	other threads:[~2007-06-12  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 14:12 PATCH -mm] fix create_new_namespaces() return value Cedric Le Goater
2007-06-11 16:22 ` Badari Pulavarty
2007-06-12  7:49   ` Cedric Le Goater [this message]
2007-06-12 12:19   ` Cedric Le Goater

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=466E4FF6.8040709@free.fr \
    --to=legoater@free.fr \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=serue@us.ibm.com \
    --cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.