From: "Serge E. Hallyn" <serue@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: [PATCH 0/6] file capabilities cleanups: introduction
Date: Fri, 26 Sep 2008 22:27:44 -0400 [thread overview]
Message-ID: <1222482472-12847-1-git-send-email-serue@us.ibm.com> (raw)
Following is a set of file capabilities cleanups. The first
two patches are a repost of my previous patches which
introduce a no_file_caps boot option, and remove the
CONFIG_SECURITY_FILE_CAPABILITIES config option. The rest
of the patches both clean up some of the capabilities code
and reduce the kernel size (since enabling file capabilities
grew it).
Andrew Morgan, if you have a moment, please do take a close look
and make sure I'm not doing anything stupid/wrong in the cleanups!
However ltp shows no difference with and without the patchset.
Following are the kernel sizes after some of the patches.
original, pre-patch, with file capabilities compiled out:
text data bss dec hex filename
4188468 234432 316472 4739372 48512c vmlinux
original, pre-patch, with file capabilities compiled in:
4189356 234432 316472 4740260 4854a4 vmlinux
plain with fcaps always-on:
4189392 234456 316472 4740320 4854e0 vmlinux
with non-inline cap_safe_nice:
4189112 234456 316472 4740040 4853c8 vmlinux
with cleaned-up setcap:
4189120 234456 316472 4740048 4853d0 vmlinux
with needless check for target!=current removed from cap_capset:
4189104 234456 316472 4740032 4853c0 vmlinux
with needless(?) bprm_clear_caps calls removed:
4189088 234456 316472 4740016 4853b0 vmlinux
thanks,
-serge
next reply other threads:[~2008-09-27 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 2:27 Serge E. Hallyn [this message]
2008-09-27 2:27 ` [PATCH 1/6] file capabilities: add no_file_caps switch (v3) Serge E. Hallyn
2008-09-27 2:27 ` [PATCH 2/6] file capabilities: remove CONFIG_SECURITY_FILE_CAPABILITIES Serge E. Hallyn
2008-09-27 2:27 ` [PATCH 3/6] file capabilities: uninline cap_safe_nice Serge E. Hallyn
2008-09-27 2:27 ` [PATCH 4/6] file capabilities: clean up setcap code Serge E. Hallyn
2008-09-27 2:27 ` [PATCH 5/6] file capabilities: remove needless inline functions Serge E. Hallyn
2008-09-27 2:27 ` [PATCH 6/6] file capabilities: remove needless (?) bprm_clear_caps calls Serge E. Hallyn
2008-09-27 2:27 ` Serge E. Hallyn
2008-09-27 2:27 ` Serge E. Hallyn
2008-09-27 4:39 ` [PATCH 5/6] file capabilities: remove needless inline functions Andrew G. Morgan
2008-09-27 13:40 ` Serge E. Hallyn
2008-09-29 21:53 ` Serge E. Hallyn
2008-09-27 4:58 ` [PATCH 4/6] file capabilities: clean up setcap code Andrew G. Morgan
2008-09-27 13:43 ` Serge E. Hallyn
2008-09-27 4:26 ` [PATCH 3/6] file capabilities: uninline cap_safe_nice Andrew G. Morgan
2008-09-27 5:27 ` James Morris
2008-09-27 4:25 ` [PATCH 2/6] file capabilities: remove CONFIG_SECURITY_FILE_CAPABILITIES Andrew G. Morgan
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=1222482472-12847-1-git-send-email-serue@us.ibm.com \
--to=serue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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®