ius-coredev team mailing list archive

[Andrew Garner <1398199@xxxxxxxxxxxxxxxxxx>]

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.6.22+ 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.6.22 to guard against this case and avoids the
crash noted in MySQL bug 75245.


** Patch added: "Fix for MySQL bug #75245"
   https://bugs.launchpad.net/ius/+bug/1398199/+attachment/4283602/+files/mysql_bug_75245_5622.patch

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/1398199

Title:
  UPDATE REQUEST: mysql56u 5.6.22 is available upstream

Status in IUS Community Project:
  In Progress

Bug description:
  New Source from
  http://dev.mysql.com/downloads/mysql/5.6.html#downloads

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/1398199/+subscriptions