From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Iulia Manda <iulia.manda21@gmail.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Serge Hallyn <serge.hallyn@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Peter Zijlstra <peterz@infradead.org>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH v2] kernel: Conditionally support non-root users, groups and capabilities
Date: Thu, 29 Jan 2015 19:59:09 +0100 [thread overview]
Message-ID: <CAMuHMdVeixAcLEb2JZLyPyjEr7Y2nLpmpOLdX90Xjon9jTFquw@mail.gmail.com> (raw)
In-Reply-To: <20150129184311.GA6404@winterfell>
Hi Iulia,
On Thu, Jan 29, 2015 at 7:43 PM, Iulia Manda <iulia.manda21@gmail.com> wrote:
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
> index 68b68d7..b2d2116 100644
> --- a/arch/s390/Kconfig
> +++ b/arch/s390/Kconfig
> @@ -324,6 +324,7 @@ config COMPAT
> select COMPAT_BINFMT_ELF if BINFMT_ELF
> select ARCH_WANT_OLD_COMPAT_IPC
> select COMPAT_OLD_SIGACTION
> + select NON_ROOT
> @@ -10,6 +10,7 @@ config LUSTRE_FS
> + select NON_ROOT
> @@ -6,6 +6,7 @@ config NFSD
> + select NON_ROOT
> config BSD_PROCESS_ACCT
> bool "BSD Process Accounting"
> + select NON_ROOT
> config TASKSTATS
> + select NON_ROOT
Is there a specific reason why you chose to use "select NON_ROOT"
instead of "depends on NON_ROOT" for all these options?
As configuring NON_ROOT=n is quite a drastic decision, I don't
think you should let that be revertable such easily by all those selects.
> @@ -1140,6 +1142,7 @@ config CHECKPOINT_RESTORE
>
> menuconfig NAMESPACES
> bool "Namespaces support" if EXPERT
> + depends on NON_ROOT
> @@ -1352,11 +1355,25 @@ menuconfig EXPERT
>
> config UID16
> bool "Enable 16-bit UID system calls" if EXPERT
> - depends on HAVE_UID16
> + depends on HAVE_UID16 && NON_ROOT
Ah, finally a few "depends on".
> +config NON_ROOT
> + bool "Multiple users, groups and capabilities support" if EXPERT
> + default y
> + help
> + This option enables support for non-root users, groups and
> + capabilities.
> +
> + If you say N here, all processes will run with UID 0, GID 0, and all
> + possible capabilities. Saying N here also compiles out support for
> + system calls related to UIDs, GIDs, and capabilities, such as setuid,
> + setgid, and capset.
> +
> + If unsure, say Y here.
I think it would be clearer to use positive instead of negative logic.
What about calling the option "MULTIUSER" instead of "NON_ROOT"?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-01-29 18:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 18:43 Iulia Manda
2015-01-29 18:59 ` Geert Uytterhoeven [this message]
2015-01-29 20:01 ` josh
2015-01-29 20:16 ` Geert Uytterhoeven
2015-01-29 23:44 ` Casey Schaufler
2015-01-30 0:32 ` Paul E. McKenney
2015-01-30 1:25 ` Casey Schaufler
2015-01-30 1:36 ` Paul E. McKenney
2015-01-30 2:25 ` Casey Schaufler
2015-01-30 7:07 ` Paul E. McKenney
2015-01-30 19:13 ` josh
2015-01-30 19:48 ` Casey Schaufler
2015-01-30 20:20 ` Austin S Hemmelgarn
2015-01-30 21:40 ` Josh Triplett
2015-01-30 21:56 ` Richard Weinberger
2015-01-31 23:30 ` Paul E. McKenney
2015-01-31 23:33 ` Richard Weinberger
2015-02-01 19:45 ` Paul E. McKenney
2015-01-31 17:00 ` Jarkko Sakkinen
2015-01-30 0:43 ` josh
2015-01-30 2:05 ` Casey Schaufler
2015-01-30 21:04 ` Josh Triplett
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=CAMuHMdVeixAcLEb2JZLyPyjEr7Y2nLpmpOLdX90Xjon9jTFquw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--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 \
/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®