[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111110142723.GA7727@sergelap>
Date: Thu, 10 Nov 2011 08:27:24 -0600
From: "Serge E. Hallyn" <serge.hallyn@...onical.com>
To: Matt Helsley <matthltc@...ibm.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, richard@....at,
containers@...ts.linux-foundation.org, oleg@...hat.com,
eparis@...hat.com, linux-kernel@...r.kernel.org,
dhowells@...hat.com, ebiederm@...ssion.com
Subject: Re: [PATCH 1/6] user namespace: make signal.c respect user
namespaces (v4)
Quoting Matt Helsley (matthltc@...ibm.com):
> On Wed, Nov 09, 2011 at 08:18:53AM -0600, Serge E. Hallyn wrote:
> > Quoting Andrew Morton (akpm@...ux-foundation.org):
> > > On Fri, 4 Nov 2011 22:24:37 +0000
> > > Serge Hallyn <serge@...lyn.com> wrote:
> > >
> > > > +static inline void fixup_uid(struct siginfo *info, struct task_struct *t)
>
> nit: Seems like the function name itself needs a fixup. I can imagine a
> user-ns-unaware kernel developer thinking this when they see code calling
> this function:
>
> <naive>
> Gosh, why is the uid broken? I have no idea what this does or when it
> would be needed. Why hasn't it been splatted all over the kernel? Who broke
> it?
> </naive>
>
> You can't even tell from the name that it's for user namespaces.
Heh, my first reaction was that you're over-reacting, but you're probably
right. I don't want to conflict with the 'user_ns_map_uids' function,
so how about userns_fixup_signal_uids()? Pls let me know if you have a
better name, otherwise I'll switch to this one.
thanks,
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists