Files
MaxScale/server/core
Markus Makela 689366b6b7 Fix possible writes to closed DCBs
When persistent connections were used, it was possible that the injection
of COM_CHANGE_USER statements caused a crash when a DCB in the wrong state
was accessed.

For MySQL protocol modules, the `data` member of the client DCB points to
the shared session data, a MYSQL_session struct, but for sessions in the
persistent pool, it points to NULL. The boolean, `was_persistent`, tells
whether a DCB was just taken from the pool or it has been in use.

The `was_persistent` status wasn't properly reset for connections that
were put into the pool which caused a COM_CHANGE_USER statement to be
injected for stale connections in the pool which caused a crash when the
NULL `data` member was accessed.
2016-11-08 09:24:00 +02:00
..
2016-10-14 19:50:54 +03:00
2016-11-03 09:35:49 +02:00
2016-08-11 12:44:07 +03:00
2016-10-14 19:50:54 +03:00
2016-10-21 18:33:35 +03:00
2016-10-14 19:50:54 +03:00
2016-10-21 18:33:35 +03:00
2016-11-08 09:24:00 +02:00
2016-08-17 10:06:35 +03:00
2016-10-14 15:42:02 +03:00
2016-10-14 19:50:54 +03:00
2016-10-27 14:50:22 +03:00
2016-10-15 11:18:14 +03:00
2016-10-21 18:33:35 +03:00
2016-10-17 12:17:09 +03:00
2016-10-14 19:50:54 +03:00
2016-10-14 19:50:54 +03:00
2016-10-14 15:55:33 +03:00
2016-10-14 19:50:54 +03:00
2016-10-14 19:50:54 +03:00
2016-10-21 18:33:35 +03:00
2016-10-14 13:48:10 +03:00
2016-10-24 14:00:51 +03:00
2016-10-14 13:48:10 +03:00
2016-10-17 12:17:09 +03:00
2016-10-21 18:33:35 +03:00
2016-11-07 16:19:56 +02:00
2016-10-14 19:50:54 +03:00
2016-10-14 13:48:10 +03:00
2016-10-27 15:55:26 +03:00
2016-11-03 09:35:49 +02:00