From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [patch -mm] utsname namespace : fix unshare when CONFIG_UTS_NS is not set
Date: Thu, 14 Sep 2006 10:51:18 -0500 [thread overview]
Message-ID: <20060914155118.GA4337@sergelap.austin.ibm.com> (raw)
In-Reply-To: <4509771B.9070204@fr.ibm.com>
Quoting Cedric Le Goater (clg@fr.ibm.com):
> If the kernel is not configured with the CONFIG_UTS_NS, unshare of
> ipc namespace will fail and return -EINVAL.
>
> The patch changes the dummy unshare_utsname() to check the clone flags
> before returning.
>
> Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
thanks,
-serge
> Cc: Andrew Morton <akpm@osdl.org>
> Cc: Serge E. Hallyn <serue@us.ibm.com>
> Cc: Linux Containers <containers@lists.osdl.org>
>
> ---
> include/linux/utsname.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> Index: 2.6.18-rc6-mm2/include/linux/utsname.h
> ===================================================================
> --- 2.6.18-rc6-mm2.orig/include/linux/utsname.h
> +++ 2.6.18-rc6-mm2/include/linux/utsname.h
> @@ -60,8 +60,12 @@ static inline void put_uts_ns(struct uts
> static inline int unshare_utsname(unsigned long unshare_flags,
> struct uts_namespace **new_uts)
> {
> - return -EINVAL;
> + if (unshare_flags & CLONE_NEWUTS)
> + return -EINVAL;
> +
> + return 0;
> }
> +
> static inline int copy_utsname(int flags, struct task_struct *tsk)
> {
> return 0;
prev parent reply other threads:[~2006-09-14 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 15:36 Cedric Le Goater
2006-09-14 15:51 ` Serge E. Hallyn [this message]
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=20060914155118.GA4337@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.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
all inboxes | Powered by JetHome®