UPDATE REQUEST: mysql55 5.5.41 is available upstream

[bharper]

New Source from http://dev.mysql.com/downloads/mysql/5.5.html#downloads

[Carl George (carl.george)]

This package has been built and will be moved to the testing repos tonight.

[Carl George (carl.george)]

This package will move to the stable repos tonight. It may take up to 24 hours to sync to all mirrors.

[Carl George (carl.george)]

We have been notified that there is a serious bug in this version of MySQL that can cause a segfault. Please downgrade to 5.5.40-2 if you are affected. We will be pulling 5.5.41-1 from the stable repos.

http://bugs.mysql.com/bug.php?id=75245

[Andrew Garner (muzazzi)]

The critical bug referenced here in bugs.mysql.com/75245 is caused by a NULL dereference originating in new "ib_warn_row_too_big()" code in the InnoDB storage engine (storage/innobase/handler/ha_innodb.cc). This manifests if a table is created that might exceed the maximum row length if fully populated. Details of the limitations in the InnoDB maximum row size are detailed in this Percona blog post:

http://www.percona.com/blog/2011/04/07/innodb-row-size-limitation/

When innodb_strict_mode is enabled, the server refuses to allow such tables to be created. If a table is created with innodb_strict_mode = off (the default), 5.5.41+ now sends the client a warning. However there are certain corner cases where there may not be a valid client (i.e. during innodb recovery) and when the table is loaded InnoDB tries to send warnings on a "NULL" user connection. This causes a null dereference and the server will segfault.

Attached is a patch for 5.5.41 to guard against this case and avoids the crash noted in MySQL bug 75245.

[bharper (bharper)]

Updated packages with this patch have been built and are available in the testing repo.

-Ben

[bharper (bharper)]

Correction, the updated package will be placed in the testing repos after tonight's automation run.

-Ben

[Carl George (carl.george)]

The updated packages will move to the stable repos tonight. It may take up to 24 hours to sync to all mirrors.

[Carl George (carl.george)]

Andrew's patch is now in the upstream 5.5.42 source, so we will be able to drop the patch from the next build of mysql55.

https://bugs.launchpad.net/ius/+bug/1417550