From: Andrew Morton <akpm@linux-foundation.org>
To: Iulia Manda <iulia.manda21@gmail.com>
Cc: geert@linux-m68k.org, paulmck@linux.vnet.ibm.com,
josh@joshtriplett.org, peterz@infradead.org, mhocko@suse.cz,
linux-kernel@vger.kernel.org, serge.hallyn@canonical.com,
dvhart@linux.intel.com, tim.bird@sonymobile.com
Subject: Re: [PATCH v4] kernel: Conditionally support non-root users, groups and capabilities
Date: Fri, 20 Feb 2015 16:11:32 -0800 [thread overview]
Message-ID: <20150220161132.d636e85fd4f9698d889243d2@linux-foundation.org> (raw)
In-Reply-To: <20150211150336.GA2406@winterfell>
On Wed, 11 Feb 2015 17:03:36 +0200 Iulia Manda <iulia.manda21@gmail.com> wrote:
> There are a lot of embedded systems that run most or all of their functionality
> in init, running as root:root. For these systems, supporting multiple users is
> not necessary.
>
> This patch adds a new symbol, CONFIG_MULTIUSER, that makes support for non-root
> users, non-root groups, and capabilities optional. It is enabled under
> CONFIG_EXPERT menu.
>
> When this symbol is not defined, UID and GID are zero in any possible case
> and processes always have all capabilities.
>
> The following syscalls are compiled out: setuid, setregid, setgid,
> setreuid, setresuid, getresuid, setresgid, getresgid, setgroups, getgroups,
> setfsuid, setfsgid, capget, capset.
>
> Also, groups.c is compiled out completely.
>
> In kernel/capability.c, capable function was moved in order to avoid adding two
> ifdef blocks.
>
> This change saves about 25 KB on a defconfig build.
>
> The kernel was booted in Qemu. All the common functionalities work. Adding
> users/groups is not possible, failing with -ENOSYS.
>
> Bloat-o-meter output:
> add/remove: 7/87 grow/shrink: 19/397 up/down: 1675/-26325 (-24650)
The objective seems OK to me - in some kernel applications non-root
users are never needed and it's better to not force those systems to
carry a lump of code they will never use.
How significant is the 25k saving? On a realistic kernel build for
such a target, what proportion of kernel memory usage are we talking
about here?
Did you look at moving sys_setregid into groups.c (or elsewhere) to
save an ifdef?
I assume that more savings can be squeezed out - there will be fields
in the task_struct and other places which will never be used. ifdefing
those out will get messy. Have you done any investigation here?
next prev parent reply other threads:[~2015-02-21 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 15:03 Iulia Manda
2015-02-21 0:11 ` Andrew Morton [this message]
2015-02-24 0:53 ` josh
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=20150220161132.d636e85fd4f9698d889243d2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dvhart@linux.intel.com \
--cc=geert@linux-m68k.org \
--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 \
--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
Powered by JetHome