From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Joshua Brindle <jbrindle@tresys.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: Multiple small fixes to policycoreutils
Date: Mon, 20 Nov 2006 12:10:59 -0500 [thread overview]
Message-ID: <4561E1A3.8070306@mentalrootkit.com> (raw)
In-Reply-To: <455DA4E8.5050600@redhat.com>
Daniel J Walsh wrote:
> Karl MacMillan wrote:
>> Joshua Brindle wrote:
>>>> From: Karl MacMillan [mailto:kmacmillan@mentalrootkit.com]
>>>> Daniel J Walsh wrote:
>>>>> Joshua Brindle wrote:
>>>>>> Karl MacMillan wrote:
>>>> <snip>
>>>>
>>>>>>> What about a top-level USE_PIE makefile variable that directs all
>>>>>>> sub-Makefiles to set PIE flags if appropriate for that module? By
>>>>>>> default it would be off. This gets the behavior you want without
>>>>>>> having to carry a patch and keeps the current behavior.
>>>>>>>
>>>>>> No patch necessary, like Chris said make CFLAGS="-fPIE -02 -Werror
>>>>>> -Wall" LDFLAGS="-pie"
>>>>>>
>>>>>> done and done.
>>>>>>
>>>>> No, because then all compiled apps become -pie. We only
>>>> want this on
>>>>> the daemons.
>>>>>
>>>> What about this instead?
>>>
>>> Why doesn't make CFLAGS="-fPIE -02 -Werror -Wall" LDFLAGS="-pie"
>>> work? Why does itmatter if everything is built pie?
>>>
>>
>> There are performance costs associated with pie, particularly at
>> startup. Talking to Dan though, he doesn't think it is enough to not
>> just build everything as pie.
>>
>> Resend below that I will apply unless there are other objections.
>>
Committed as policycoreutils 1.33.2.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-11-20 17:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 15:06 Multiple small fixes to policycoreutils Daniel J Walsh
2006-11-14 16:13 ` Christopher J. PeBenito
2006-11-14 16:18 ` Daniel J Walsh
2006-11-14 19:19 ` Christopher J. PeBenito
2006-11-14 20:09 ` Daniel J Walsh
2006-11-15 18:34 ` Karl MacMillan
2006-11-15 19:38 ` Joshua Brindle
2006-11-15 20:16 ` Daniel J Walsh
2006-11-15 20:18 ` Joshua Brindle
2006-11-15 22:01 ` Karl MacMillan
2006-11-16 0:05 ` Joshua Brindle
2006-11-16 22:15 ` Karl MacMillan
2006-11-17 0:50 ` Joshua Brindle
2006-11-17 12:02 ` Daniel J Walsh
2006-11-20 17:10 ` Karl MacMillan [this message]
2006-11-20 17:36 ` More " Daniel J Walsh
2006-11-20 18:28 ` Joshua Brindle
2006-11-20 20:14 ` Karl MacMillan
2006-11-20 20:25 ` Stephen Smalley
2006-11-21 3:54 ` Joshua Brindle
2006-11-21 14:35 ` Karl MacMillan
2006-11-21 14:37 ` Karl MacMillan
2006-11-20 21:58 ` Daniel J Walsh
2006-11-21 13:53 ` Stephen Smalley
2006-11-22 19:16 ` Daniel J Walsh
2006-11-22 19:22 ` Joshua Brindle
2006-11-22 20:05 ` Daniel J Walsh
2006-11-22 20:31 ` Joshua Brindle
2006-11-22 21:21 ` Daniel J Walsh
2006-11-28 19:37 ` Joshua Brindle
2006-11-29 21:18 ` Joshua Brindle
2006-11-22 20:06 ` Daniel J Walsh
2006-11-22 20:34 ` Joshua Brindle
2006-11-22 21:10 ` Daniel J Walsh
2006-11-22 20:07 ` Daniel J Walsh
2006-11-22 20:35 ` Joshua Brindle
2006-11-22 20:08 ` Daniel J Walsh
2006-11-22 20:36 ` Joshua Brindle
2006-11-22 20:10 ` Daniel J Walsh
2006-11-22 20:36 ` Joshua Brindle
2006-11-22 21:07 ` Daniel J Walsh
2006-11-27 13:39 ` Joshua Brindle
2006-11-21 21:13 ` Stephen Smalley
2006-11-15 16:13 ` Multiple " Joshua Brindle
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=4561E1A3.8070306@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.