linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "stefan.seyfried@googlemail.com" <stefan.seyfried@googlemail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: test-mesh-crypto segfaults
Date: Tue, 5 Nov 2019 16:31:00 +0000	[thread overview]
Message-ID: <229f92060a132ddbbaae9b3be74710dcdf829f99.camel@intel.com> (raw)
In-Reply-To: <c67c9cd7-ecdd-396e-ab7b-bb8716733690@message-id.googlemail.com>

Hi Stefan,

On Tue, 2019-11-05 at 16:24 +0100, Stefan Seyfried wrote:
> Am 05.11.19 um 10:53 schrieb Stefan Seyfried:
> > Hi Brian,
> > 
> > One thing I forgot to mention explicitly: this is the recently released bluez-5.52 tarball, not git
> > master(!).
> > Also note that openSUSE Factory use LTO by default now.
> 
> LTO seems to trigger the problem, see
> https://bugzilla.opensuse.org/show_bug.cgi?id=1155889#c6
> for an explanation of the issue and a suggested patch that will fix / work around the issue.

Thank you for your very thorough analysis.  We are looking at it now.

> 
> Best regards,

      reply	other threads:[~2019-11-05 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 21:16 test-mesh-crypto segfaults Stefan Seyfried
2019-11-04 22:11 ` Gix, Brian
2019-11-04 22:26   ` Gix, Brian
2019-11-05  9:53   ` Stefan Seyfried
2019-11-05 15:24     ` Stefan Seyfried
2019-11-05 16:31       ` Gix, Brian [this message]

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=229f92060a132ddbbaae9b3be74710dcdf829f99.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.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;
as well as URLs for NNTP newsgroup(s).