Ubuntu
mysql-5.5 package

  1. Trusty (14.04)
  2. Bug #1427406
  3. Comment #35

Comment 35 for bug 1427406

Revision history for this message
dann frazier (dannf) wrote : Re: [Bug 1427406] Re: data corruption on arm64 and ppc64el

On Wed, Oct 25, 2017 at 7:56 AM, ChristianEhrhardt
<email address hidden> wrote:
> Vivid is end of life, marking as won't fix.
> There is one "lost" update - which was [1].
> But that was lost in a follow on security update - see c#26 + c#27 for details.
>
> That makes mysql-5.6 in Trusty "triaged" instead of "Fix Committed"
> It does not seem a later stable release has intregated that particular fix you had - maybe an alternative.
> @Dannf - any plan to reroll these - or will this go to Won't Fix?

I believe this was later fixed, in a different way, by an upstream
point release.

From https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-27.html :
 "InnoDB: A data corruption occurred on ARM64. GCC builtins did not
issue the correct fences when setting or unsetting the lock word. (Bug
#21102971, Bug #76135)"

I'll therefore go ahead and mark trusty as Fix Released.