Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: test-mesh-crypto segfaults
From:   Stefan Seyfried <stefan.seyfried@googlemail.com>
To:     "Gix, Brian" <brian.gix@intel.com>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc:     "Stotland, Inga" <inga.stotland@intel.com>
References: <5f75011d-a157-cab2-72df-0209f7a30f21@message-id.googlemail.com>
 <70299d5df034aa0174a9263ea8736b56fd9bbd02.camel@intel.com>
 <cf7105b3-c623-5583-6cb5-2d04f22c9766@message-id.googlemail.com>
Message-ID: <c67c9cd7-ecdd-396e-ab7b-bb8716733690@message-id.googlemail.com>
Date:   Tue, 5 Nov 2019 16:24:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <cf7105b3-c623-5583-6cb5-2d04f22c9766@message-id.googlemail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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.

Best regards,
-- 
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman