From: Saul Wold <sgw@linux.intel.com>
To: akuster808 <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/5] security_flags: disable pie support for libaio, blktrace and ltp
Date: Wed, 14 Jan 2015 10:59:51 -0800 [thread overview]
Message-ID: <54B6BCA7.7080402@linux.intel.com> (raw)
In-Reply-To: <54B6BBA9.20501@gmail.com>
On 01/14/2015 10:55 AM, akuster808 wrote:
> Do we need this for Dizzy?
>
No this is not needed for dizzy, this is something that happened after I
updated libaio, so it's just affects the new libaio with blktrace and ltp.
Sau!
> - armin
>
> On 01/09/2015 02:51 PM, Saul Wold wrote:
>> libaio when built with pie and fpie does not link correctly with
>> blktrace or ltp
>> so we need to disable those flags until a better solution comes along.
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>> meta/conf/distro/include/security_flags.inc | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/meta/conf/distro/include/security_flags.inc
>> b/meta/conf/distro/include/security_flags.inc
>> index 840f68a..d6f7e9c 100644
>> --- a/meta/conf/distro/include/security_flags.inc
>> +++ b/meta/conf/distro/include/security_flags.inc
>> @@ -16,6 +16,7 @@ SECURITY_CFLAGS_pn-lttng-tools_arm =
>> "${SECURITY_NO_PIE_CFLAGS}"
>>
>> SECURITY_CFLAGS_pn-aspell = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-beecrypt = "${SECURITY_NO_PIE_CFLAGS}"
>> +SECURITY_CFLAGS_pn-blktrace = "${SECURITY_NO_PIE_CFLAGS}"
>> # Curl seems to check for FORTIFY_SOURCE in CFLAGS, but even assigned
>> # to CPPFLAGS it gets picked into CFLAGS in bitbake.
>> #TARGET_CPPFLAGS_pn-curl += "-D_FORTIFY_SOURCE=2"
>> @@ -43,6 +44,7 @@ SECURITY_CFLAGS_pn-gst-plugins-gl =
>> "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-gstreamer1.0-plugins-good =
>> "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-harfbuzz = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-kexec-tools = "${SECURITY_NO_PIE_CFLAGS}"
>> +SECURITY_CFLAGS_pn-libaio = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libcap = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libgcc = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libid3tag = "${SECURITY_NO_PIE_CFLAGS}"
>> @@ -51,6 +53,7 @@ SECURITY_CFLAGS_pn-libglu = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libpcap = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libpcre = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libproxy = "${SECURITY_NO_PIE_CFLAGS}"
>> +SECURITY_CFLAGS_pn-ltp = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-lttng-ust = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-mesa = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-mesa-gl = "${SECURITY_NO_PIE_CFLAGS}"
>>
next prev parent reply other threads:[~2015-01-14 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 22:51 [PATCH 0/5] Patch and Upgrades Saul Wold
2015-01-09 22:51 ` [PATCH 1/5 v2] usbutils: Add version 008 Saul Wold
2015-01-09 22:51 ` [PATCH 2/5 v2] gnu-efi: Upgrade to 3.0.1 Saul Wold
2015-01-09 22:51 ` [PATCH 3/5] security_flags: disable pie support for libaio, blktrace and ltp Saul Wold
2015-01-14 18:55 ` akuster808
2015-01-14 18:59 ` Saul Wold [this message]
2015-01-09 22:51 ` [PATCH 4/5] libaio: Upgrade to 0.3.110 Saul Wold
2015-01-09 22:51 ` [PATCH 5/5] glibc: Fix up minimal build with libc-libm Saul Wold
2015-01-14 18:54 ` akuster808
2015-01-14 19:00 ` Saul Wold
2015-01-14 23:27 ` Richard Purdie
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=54B6BCA7.7080402@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.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