From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
ebiederm@xmission.com, herbert@13thfloor.at, dev@sw.ru,
linux-kernel@vger.kernel.org, sam@vilain.net, xemul@sw.ru,
clg@us.ibm.com, frankeh@us.ibm.com
Subject: Re: [PATCH 7/7] uts namespaces: Implement CLONE_NEWUTS flag
Date: Mon, 1 May 2006 16:11:09 -0500 [thread overview]
Message-ID: <20060501211109.GA21799@sergelap.austin.ibm.com> (raw)
In-Reply-To: <1146515316.32079.27.camel@localhost.localdomain>
Quoting Dave Hansen (haveblue@us.ibm.com):
> On Mon, 2006-05-01 at 14:53 -0500, Serge E. Hallyn wrote:
> > +struct uts_namespace *clone_uts_ns(struct uts_namespace *old_ns)
> > +{
> > + 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);
> > + }
> > + return ns;
> > +}
>
> Very small nit...
>
> Would this memcpy be more appropriate as a strncpy()?
>
> > +int unshare_utsname(unsigned long unshare_flags, struct uts_namespace **new_uts)
> > +{
> > + if (unshare_flags & CLONE_NEWUTS) {
> > + if (!capable(CAP_SYS_ADMIN))
> > + return -EPERM;
> > +
> > + *new_uts = clone_uts_ns(current->uts_ns);
> > + if (!*new_uts)
> > + return -ENOMEM;
> > + }
> > +
> > + return 0;
> > +}
>
> Would it be a bit nicer to use the ERR_PTR() mechanism here instead of
> the double-pointer bit?
>
> I've always liked those a bit better because there's no hiding the fact
> of what is actually a return value from a function.
I agree. I was (grudgingly) copying the style from the other helpers
in fs/fork.c. Then I had to pull it out so it could cleanly return
-ENOMEM if !CONFIG_UTS, but I expect CONFIG_UTS to be yanked, and
this fn to be returned to fs/fork.c...
Might be worth a separate patch to change over all those helpers in
fork.c? (I think they were all brought in along with the sys_unshare
syscall)
Agreed on all your other points, thanks.
-serge
next prev parent reply other threads:[~2006-05-02 0:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 19:53 [PATCH 2/7] uts namespaces: switch to using uts namespaces Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 3/7] uts namespaces: use init_utsname when appropriate Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 1/7] uts namespaces: introduce temporary helpers Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 4/7] uts namespaces: implement utsname namespaces Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 5/7] uts namespaces: sysctl hack Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 6/7] uts namespaces: remove system_utsname Serge E. Hallyn
2006-05-01 19:53 ` [PATCH 7/7] uts namespaces: Implement CLONE_NEWUTS flag Serge E. Hallyn
2006-05-01 20:28 ` Dave Hansen
2006-05-01 21:11 ` Serge E. Hallyn [this message]
2006-05-01 21:58 ` Dave Hansen
2006-05-02 17:32 ` Serge E. Hallyn
2006-05-02 8:55 ` Eric W. Biederman
2006-05-02 6:55 ` Andi Kleen
2006-05-02 8:03 ` Eric W. Biederman
2006-05-02 8:17 ` Andi Kleen
2006-05-02 8:48 ` Eric W. Biederman
2006-05-02 17:20 ` Serge E. Hallyn
2006-05-02 17:30 ` Andi Kleen
2006-05-03 16:11 ` Serge E. Hallyn
2006-05-03 16:19 ` Serge E. Hallyn
2006-05-05 6:44 ` Herbert Poetzl
2006-05-05 12:17 ` Serge E. Hallyn
2006-05-05 11:02 ` Andi Kleen
2006-05-05 11:43 ` Serge E. Hallyn
2006-05-05 14:31 ` Andi Kleen
2006-05-05 15:55 ` Eric W. Biederman
2006-05-01 19:53 [PATCH 0/7] uts namespaces: Introduction Serge E. Hallyn
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=20060501211109.GA21799@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=clg@us.ibm.com \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=frankeh@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@vilain.net \
--cc=xemul@sw.ru \
/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®