public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg@fr.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Herbert Poetzl <herbert@13thfloor.at>,
	pbadari@us.ibm.com, containers@lists.osdl.org,
	ebiederm@xmission.com, serue@us.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] create_new_namespaces: fix improper return of NULL
Date: Tue, 19 Jun 2007 16:05:00 +0200	[thread overview]
Message-ID: <4677E28C.5050304@fr.ibm.com> (raw)
In-Reply-To: <20070619135129.GA27343@tv-sign.ru>

Oleg Nesterov wrote:
> Untested.
> 
> dup_mnt_ns() and clone_uts_ns() return NULL on failure. This is wrong,
> create_new_namespaces() uses ERR_PTR() to catch an error. This means
> that the subsequent create_new_namespaces() will hit BUG_ON() in
> copy_mnt_ns() or copy_utsname().

I sent one just like it :

	http://lkml.org/lkml/2007/6/12/142

but your changelog is worth adding. much better than mine.

thanks,

C. 

> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
> 
> --- ns/fs/namespace.c~1_NS_NULL	2007-05-21 13:57:56.000000000 +0400
> +++ ns/fs/namespace.c	2007-06-19 17:26:35.000000000 +0400
> @@ -1457,7 +1457,7 @@ static struct mnt_namespace *dup_mnt_ns(
> 
>  	new_ns = kmalloc(sizeof(struct mnt_namespace), GFP_KERNEL);
>  	if (!new_ns)
> -		return NULL;
> +		return ERR_PTR(-ENOMEM);
> 
>  	atomic_set(&new_ns->count, 1);
>  	INIT_LIST_HEAD(&new_ns->list);
> @@ -1471,7 +1471,7 @@ static struct mnt_namespace *dup_mnt_ns(
>  	if (!new_ns->root) {
>  		up_write(&namespace_sem);
>  		kfree(new_ns);
> -		return NULL;
> +		return ERR_PTR(-ENOMEM);
>  	}
>  	spin_lock(&vfsmount_lock);
>  	list_add_tail(&new_ns->list, &new_ns->root->mnt_list);
> --- ns/kernel/utsname.c~1_NS_NULL	2007-05-21 13:57:59.000000000 +0400
> +++ ns/kernel/utsname.c	2007-06-19 17:35:22.000000000 +0400
> @@ -13,6 +13,7 @@
>  #include <linux/uts.h>
>  #include <linux/utsname.h>
>  #include <linux/version.h>
> +#include <linux/err.h>
> 
>  /*
>   * Clone a new ns copying an original utsname, setting refcount to 1
> @@ -24,10 +25,11 @@ static struct uts_namespace *clone_uts_n
>  	struct uts_namespace *ns;
> 
>  	ns = kmalloc(sizeof(struct uts_namespace), GFP_KERNEL);
> -	if (ns) {
> -		memcpy(&ns->name, &old_ns->name, sizeof(ns->name));
> -		kref_init(&ns->kref);
> -	}
> +	if (!ns)
> +		return ERR_PTR(-ENOMEM);
> +
> +	memcpy(&ns->name, &old_ns->name, sizeof(ns->name));
> +	kref_init(&ns->kref);
>  	return ns;
>  }
> 
> 
> 


  reply	other threads:[~2007-06-19 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705090245.l492jZwD008756@shell0.pdx.osdl.net>
     [not found] ` <20070616191742.GA13434@MAIL.13thfloor.at>
     [not found]   ` <20070617143830.GA379@tv-sign.ru>
     [not found]     ` <20070617163004.GA553@tv-sign.ru>
2007-06-19 13:51       ` [PATCH] create_new_namespaces: fix improper return of NULL Oleg Nesterov
2007-06-19 14:05         ` Cedric Le Goater [this message]
2007-06-19 14:27           ` Oleg Nesterov
2007-06-19 15:41             ` 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=4677E28C.5050304@fr.ibm.com \
    --to=clg@fr.ibm.com \
    --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=oleg@tv-sign.ru \
    --cc=pbadari@us.ibm.com \
    --cc=serue@us.ibm.com \
    /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