From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Dennis Lan (dlan)" <dennis.yxun@gmail.com>
Cc: Atom2 <ariel.atom2@web2web.at>, xen-devel@lists.xen.org
Subject: Re: [BUG] XEN 4.3.3 - segfault in xl create for HVM with PCI passthrough
Date: Mon, 1 Dec 2014 09:38:51 +0000 [thread overview]
Message-ID: <1417426731.23604.76.camel@citrix.com> (raw)
In-Reply-To: <CAF1ZMEc=Qsrw1QPzABMAFU5n1t_JZ2nRQFQ+T8xYnxqsGX4=og@mail.gmail.com>
On Mon, 2014-12-01 at 11:34 +0800, Dennis Lan (dlan) wrote:
> On Mon, Nov 10, 2014 at 8:09 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > On Mon, 2014-11-10 at 12:44 +0100, Atom2 wrote:
> >
> >> > I'm afraid it's looking more and more like a toolchain issue. I'm not
> >> > expert on this side on things but it looks to me like you are hitting an
> >> > issue with some sort of buffer overflow check gone wrong? I think you'll
> >> > need a gcc hardening person for this one.
> >> The issue currently is with the guys at gentoo (for links please again
> >> see my latest post to the list from Sunday which also seems to confirm
> >> that the issue is not confined to 4.3.3 but also 4.4.1).
> >
> > OK, I'll wait and see what the gentoo folks have to say before looking
> > any close then, thanks.
> >
> Hi Ian
> what we found now is, the Gentoo's hardened toolchain, turn CFLAGS
> -fstack-check on by default, with this flag and compile gcc will
> result xl segfault (actually with libgcc_s.so)
> we have a patch to force gcc build libgcc(only this part) code with
> -fstack-check=no, make the segfault gone
> more info can be found at https://bugs.gentoo.org/show_bug.cgi?id=528690
Excellent, thanks for letting us know.
Just to be sure: This isn't (so far as anyone knows) the result of any
coding/build-system problem in Xen, right?
Ian.
next prev parent reply other threads:[~2014-12-01 9:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 21:25 segfault in xl create for HVM with PCI passthrough Atom2
2014-10-28 10:59 ` Ian Campbell
2014-10-28 15:39 ` Atom2
2014-10-28 16:04 ` Ian Campbell
2014-10-29 0:26 ` Atom2
2014-10-30 23:05 ` Atom2
2014-11-04 15:13 ` [BUG] XEN 4.3.3 - " Atom2
2014-11-04 15:44 ` Ian Campbell
2014-11-04 16:14 ` Atom2
2014-11-04 16:31 ` Ian Campbell
2014-11-04 16:48 ` Atom2
2014-11-05 9:33 ` Ian Campbell
2014-11-04 17:30 ` Atom2
2014-11-05 9:45 ` Ian Campbell
2014-11-05 12:01 ` Atom2
2014-11-05 12:39 ` Ian Campbell
2014-11-05 12:45 ` Andrew Cooper
2014-11-05 12:47 ` Ian Campbell
2014-11-06 15:11 ` Atom2
2014-11-10 11:16 ` Ian Campbell
2014-11-10 11:44 ` Atom2
2014-11-10 12:09 ` Ian Campbell
2014-12-01 3:34 ` Dennis Lan (dlan)
2014-12-01 9:38 ` Ian Campbell [this message]
2014-11-09 23:03 ` Atom2
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=1417426731.23604.76.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ariel.atom2@web2web.at \
--cc=dennis.yxun@gmail.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).