From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <fupan.li@windriver.com>, <jason.wessel@windriver.com>,
<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH] lxc: fixes lxc segment fault issue on arm if it is compiled with GCC 5.2
Date: Fri, 15 Jul 2016 11:03:53 -0400 [thread overview]
Message-ID: <5788FB59.3070908@windriver.com> (raw)
In-Reply-To: <1468577103-224321-1-git-send-email-fupan.li@windriver.com>
merged.
Bruce
On 2016-07-15 06:05 AM, fupan.li@windriver.com wrote:
> From: fli <fupan.li@windriver.com>
>
> If the lxc is compiled with gcc 5.2 -O2 optimization on arm,
> lxc-console/lxc-stop command always produce segment fault.
>
> The same issue also occurred on systemd: [YOCTO #8291]
>
> For lxc, after several testing, it only needs to disable
> schedule-insns2 to fix the segment fault issue.
>
> Signed-off-by: fli <fupan.li@windriver.com>
> ---
> recipes-containers/lxc/lxc_2.0.0.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/recipes-containers/lxc/lxc_2.0.0.bb b/recipes-containers/lxc/lxc_2.0.0.bb
> index 5004b9e..e436057 100644
> --- a/recipes-containers/lxc/lxc_2.0.0.bb
> +++ b/recipes-containers/lxc/lxc_2.0.0.bb
> @@ -49,6 +49,9 @@ EXTRA_OECONF += "--enable-log-src-basename"
>
> CFLAGS_append = " -Wno-error=deprecated-declarations"
>
> +# disable problematic GCC 5.2 optimizations [YOCTO #8291]
> +FULL_OPTIMIZATION_append_arm = " -fno-schedule-insns2"
> +
> PACKAGECONFIG ??= "templates \
> ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux', '', d)} \
> "
>
parent reply other threads:[~2016-07-15 15:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1468577103-224321-1-git-send-email-fupan.li@windriver.com>]
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=5788FB59.3070908@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=fupan.li@windriver.com \
--cc=jason.wessel@windriver.com \
--cc=meta-virtualization@yoctoproject.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 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.