From: josh@joshtriplett.org
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Iulia Manda <iulia.manda21@gmail.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Serge Hallyn <serge.hallyn@canonical.com>,
Darren Hart <dvhart@linux.intel.com>,
Tim Bird <tim.bird@sonymobile.com>
Subject: Re: [PATCH v3] kernel: Conditionally support non-root users, groups and capabilities
Date: Mon, 9 Feb 2015 15:42:08 -0800 [thread overview]
Message-ID: <20150209234207.GB23215@cloud> (raw)
In-Reply-To: <20150209040217.GA23091@linux.vnet.ibm.com> <CAMuHMdUNnBmFzsB8rz6afed1SzGPC8VR-Fw-y3-EQHc3jta59w@mail.gmail.com>
On Sun, Feb 08, 2015 at 10:05:25AM +0100, Geert Uytterhoeven wrote:
> Thanks for the update!
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Thanks, Geert!
On Sun, Feb 08, 2015 at 08:02:17PM -0800, Paul E. McKenney wrote:
> I presume that v4 will have your Signed-off-by. ;-)
>
> Testing on my rcutorture setup uncovered an additional required dependency,
> please see patch at the end of this email. With that fix, either separately
> or merged into your patch:
>
> Tested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> One question below about moving the definition of capable(). Either way:
Answer below.
> Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Thanks, Paul!
Based on this feedback, as well as the feedback from others on prior
versions that has since been addressed, once there's a v4 with the
changes suggested by Paul (and the signoff and acks/reviews added), I'm
going to let this patch start cooking in linux-next (after the currently
active merge window closes, of course). That'll help shake out any
other potential missing dependencies or merge issues, and leave plenty
of time for people to discuss it further before the subsequent merge
window.
> > --- a/kernel/capability.c
> > +++ b/kernel/capability.c
> > @@ -35,6 +35,7 @@ static int __init file_caps_disable(char *str)
> > }
> > __setup("no_file_caps", file_caps_disable);
> >
> > +#ifdef CONFIG_MULTIUSER
> > /*
> > * More recent versions of libcap are available from:
> > *
> > @@ -386,6 +387,24 @@ bool ns_capable(struct user_namespace *ns, int cap)
> > }
> > EXPORT_SYMBOL(ns_capable);
> >
> > +
> > +/**
> > + * capable - Determine if the current task has a superior capability in effect
> > + * @cap: The capability to be tested for
> > + *
> > + * Return true if the current task has the given superior capability currently
> > + * available for use, false if not.
> > + *
> > + * This sets PF_SUPERPRIV on the task if the capability is available on the
> > + * assumption that it's about to be used.
> > + */
> > +bool capable(int cap)
> > +{
> > + return ns_capable(&init_user_ns, cap);
> > +}
> > +EXPORT_SYMBOL(capable);
> > +#endif /* CONFIG_MULTIUSER */
> > +
> > /**
> > * file_ns_capable - Determine if the file's opener had a capability in effect
> > * @file: The file we want to check
> > @@ -412,22 +431,6 @@ bool file_ns_capable(const struct file *file, struct user_namespace *ns,
> > EXPORT_SYMBOL(file_ns_capable);
> >
> > /**
> > - * capable - Determine if the current task has a superior capability in effect
> > - * @cap: The capability to be tested for
> > - *
> > - * Return true if the current task has the given superior capability currently
> > - * available for use, false if not.
> > - *
> > - * This sets PF_SUPERPRIV on the task if the capability is available on the
> > - * assumption that it's about to be used.
> > - */
> > -bool capable(int cap)
> > -{
> > - return ns_capable(&init_user_ns, cap);
> > -}
> > -EXPORT_SYMBOL(capable);
> > -
> > -/**
>
> OK, I'll bite... Why are we moving capable()?
Consolidating from two ifdef blocks to one, based on feedback on the
initial version suggesting simplification of the ifdeffery.
- Josh Triplett
next prev parent reply other threads:[~2015-02-09 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 0:03 [PATCH v3] kernel: Conditionally support non-root users, groups and capabilities Iulia Manda
2015-02-06 13:10 ` Iulia Manda
2015-02-08 9:05 ` Geert Uytterhoeven
2015-02-09 23:42 ` josh [this message]
2015-02-10 0:33 ` Paul E. McKenney
2015-02-11 15:09 ` Iulia Manda
2015-02-09 4:02 ` Paul E. McKenney
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=20150209234207.GB23215@cloud \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=dvhart@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=iulia.manda21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=serge.hallyn@canonical.com \
--cc=tim.bird@sonymobile.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;
as well as URLs for NNTP newsgroup(s).