From: Chris Wright <chrisw@sous-sol.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
James Morris <jmorris@redhat.com>,
Andrew Morgan <morgan@kernel.org>,
Andreas Gruenbacher <agruen@suse.de>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 2/2] file capabilities: turn on by default
Date: Mon, 22 Sep 2008 15:53:21 -0700 [thread overview]
Message-ID: <20080922225315.GA610@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080922195647.GA25682@us.ibm.com>
* Serge E. Hallyn (serue@us.ibm.com) wrote:
> Here are the sizes I get with Linus' plain tree and patched
> with both of these patches:
>
> master with file capabilities: 6241626
> master w/o file capabilities: 6241595
>
> patched with file capabilities: 6241782
> patched w/o file capabilities: 6241595
>
> So actually I don't like the added size.
Different than I'm seeing here (note: defconfig has file capabilities):
text data bss dec hex filename
6804621 1017960 671900 8494481 819d91 obj64-defconfig/vmlinux
6804642 1017984 671900 8494526 819dbe obj64-defconfig-patch/vmlinux
6804069 1017960 671900 8493929 819b69 obj64-nofcap/vmlinux
6804068 1017960 671900 8493928 819b68 obj64-nofcap-patch/vmlinux
thanks,
-chris
next prev parent reply other threads:[~2008-09-22 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 18:48 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Serge E. Hallyn
2008-09-22 18:49 ` [PATCH 2/2] file capabilities: turn on by default Serge E. Hallyn
2008-09-22 19:03 ` Randy Dunlap
2008-09-22 19:56 ` Serge E. Hallyn
2008-09-22 21:09 ` Randy Dunlap
2008-09-22 22:53 ` Chris Wright [this message]
2008-09-22 19:16 ` [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Stephen Smalley
2008-09-22 20:09 ` Andreas Gruenbacher
2008-09-22 21:50 ` Serge E. Hallyn
2008-09-22 22:08 ` Andreas Gruenbacher
2008-09-23 6:48 ` James Morris
2008-09-22 22:57 ` Chris Wright
2008-09-23 15:51 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 19:54 Serge Hallyn
2008-08-28 19:54 ` [PATCH 2/2] file capabilities: turn on by default Serge Hallyn
2008-08-29 0:37 ` 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=20080922225315.GA610@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=serue@us.ibm.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