{"push_id":1244773833,"size":62,"distinct_size":5,"ref":"refs/heads/5.5-galera","head":"d40d3f4e57f375897aa29e72e947e372e6bc229d","before":"44e3046d3b09a21e21295979d6ddad9f332ebadd","commits":[{"sha":"a2770e98a6b53e6ec5d502c1e2228078ee149b3b","author":{"name":"Bjorn Munch","email":"e7011d1e5f6c758c029eb236742df04c3e5850f3@oracle.com"},"message":"Raise version number after cloning 5.5.50","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/a2770e98a6b53e6ec5d502c1e2228078ee149b3b"},{"sha":"818b3a91231119663a95b854ab1e0e2d7a2d3feb","author":{"name":"Sujatha Sivakumar","email":"6284353ba58932d8c6f7436556fbf6b3b8d68fc9@oracle.com"},"message":"Bug#12818255: READ-ONLY OPTION DOES NOT ALLOW\nINSERTS/UPDATES ON TEMPORARY TABLES\nBug#14294223: CHANGES NOT ALLOWED TO TEMPORARY TABLES ON\nREAD-ONLY SERVERS\n\nProblem:\n========\nRunning 5.5.14 in read only we can create temporary tables\nbut can not insert or update records in the table. When we\ntry we get Error 1290 : The MySQL server is running with the\n--read-only option so it cannot execute this statement.\n\nAnalysis:\n=========\nThis bug is very specific to binlog being enabled and\nbinlog-format being stmt/mixed. Standalone server without\nbinlog enabled or with row based binlog-mode works fine.\n\nHow standalone server and row based replication work:\n=====================================================\nStandalone server and row based replication mark the\ntransactions as read_write only when they are modifying\nnon temporary tables as part of their current transaction.\n\nBecause of this when code enters commit phase it checks\nif a transaction is read_write or not. If the transaction\nis read_write and global read only mode is enabled those\ntransaction will fail with 'server is read only mode'\nerror.\n\nIn the case of statement based mode at the time of writing\nto binary log a binlog handler is created and it is always\nmarked as read_write. In case of temporary tables even\nthough the engine did not mark the transaction as read_write\nbut the new transaction that is started by binlog handler is\nconsidered as read_write.\n\nHence in this case when code enters commit phase it finds\none handler which has a read_write transaction even when\nwe are modifying temporary table. This causes the server\nto throw an error when global read-only mode is enabled.\n\nFix:\n====\nAt the time of commit in \"ha_commit_trans\" if a read_write\ntransaction is found, we should check if this transaction is\ncoming from a handler other than binlog_handler. This will\nensure that there is a genuine read_write transaction being\nsent by the engine apart from binlog_handler and only then\nit should be blocked.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/818b3a91231119663a95b854ab1e0e2d7a2d3feb"},{"sha":"df7ecf64f5b9c6fb4b7789a414306de89b58bec7","author":{"name":"Sujatha Sivakumar","email":"6284353ba58932d8c6f7436556fbf6b3b8d68fc9@oracle.com"},"message":"Bug#23251517: SEMISYNC REPLICATION HANGING\n\nRevert following bug fix:\n\nBug#20685029: SLAVE IO THREAD SHOULD STOP WHEN DISK IS\nFULL\nBug#21753696: MAKE SHOW SLAVE STATUS NON BLOCKING IF IO\nTHREAD WAITS FOR DISK SPACE\n\nThis fix results in a deadlock between slave IO thread\nand SQL thread.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/df7ecf64f5b9c6fb4b7789a414306de89b58bec7"},{"sha":"cb2974156823977fd2c700c64ff0867183b3f744","author":{"name":"Shishir Jaiswal","email":"2826c01bafe13e56ad18d112d99a03b9dbc6e968@oracle.com"},"message":"Bug#21977380 - POSSIBLE BUFFER OVERFLOW ISSUES\n\nDESCRIPTION\n===========\nBuffer overflow is reported in a lot of code sections\nspanning across server, client programs, Regex libraries\netc. If not handled appropriately, they can cause abnormal\nbehaviour.\n\nANALYSIS\n========\nThe reported casea are the ones which are likely to result\nin SEGFAULT, MEMORY LEAK etc.\n\nFIX\n===\n- sprintf() has been replaced by my_snprintf() to avoid\nbuffer overflow.\n- my_free() is done after checking if the pointer isn't\n  NULL already and setting it to NULL thereafter at few\n  places.\n- Buffer is ensured to be large enough to hold the data.\n- 'unsigned int' (aka 'uint') is replaced with 'size_t'\nto avoid wraparound.\n- Memory is freed (if not done so) after its alloced and\nused.\n- Inserted assert() for size check in InnoDb memcached\ncode (from 5.6 onwards)\n- Other minor changes","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/cb2974156823977fd2c700c64ff0867183b3f744"},{"sha":"90b9c957ba6380a717aaef6285b3f1498f4a29dc","author":{"name":"Karthik Kamath","email":"4230f38087a662e0f0ff86e4670d9dc8477faf10@oracle.com"},"message":"BUG#21142859: FUNCTION UPDATING A VIEW FAILS TO FIND TABLE\n              THAT ACTUALLY EXISTS\n\nANALYSIS:\n=========\nStored functions updating a view where the view table has a\ntrigger defined that updates another table, fails reporting\nan error that the table doesn't exist.\n\nIf there is a trigger defined on a table, a variable\n'trg_event_map' will be set to a non-zero value after the\nparsed tree creation. This indicates what triggers we need to\npre-load for the TABLE_LIST when opening an associated table.\n\nDuring the prelocking phase, the variable 'trg_event_map'\nwill not be set for the view table. This value will be set\nafter the processing of triggers defined on the table. During\nthe processing of sub-statements, 'locked_tables_mode' will be\nset to 'LTM_PRELOCKED' which denotes that further locking\nof tables/functions cannot be done. This results in the other\ntable not being locked and thus further processing results in\nan error getting reported.\n\nFIX:\n====\nDuring the prelocking of view, the value of 'trg_event_map'\nof the view is copied to 'trg_event_map' of the next table\nin the TABLE_LIST. This results in the locking of tables\nassociated with the trigger as well.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/90b9c957ba6380a717aaef6285b3f1498f4a29dc"},{"sha":"8281068f72385fb559906ca14f29bd3871b8830d","author":{"name":"Balasubramanian Kandasamy","email":"2809040492f2a362e3bbbda7bddafd76c72dc76a@oracle.com"},"message":"BUG#21879694 - /VAR/LOG/MYSQLD.LOG HAS INCORRECT PERMISSIONS AFTER INSTALLING SERVER FROM REPO\n\nDescription:\nThis issue doesn't effect any default installation of repo rpms if user uses\ninit scripts that are shipped as part of package but will have trouble if\nuser tries to createdb or start server manually.\n\nAfter installing mysql-server from repository(yum,zypper) /var/log/mysqld.log\nis created with logged in user and group permissions instead of with mysql\nuser and group permissions,due to which while creating database or starting\nserver, it is failing\n\nFix:\n\nUpdated the user and group permissions of the /var/log/mysqld.log and\n/var/log/mysql/mysqld.log (for sles) files to mysql.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/8281068f72385fb559906ca14f29bd3871b8830d"},{"sha":"4de9d9c261a6f2a32e98920bbc530c473b41de07","author":{"name":"Terje Rosten","email":"638d39825236b454b996ddfc1ebe2914c2a0513b@oracle.com"},"message":"BUG#20693338 CONFLICTS WHILE INSTALLING PACKAGES WHEN LIBMYSQLCLIENT-DEVEL INSTALLED\n\nRemove mysql_config from client package to avoid conflict (file\nshipped in devel package any way).","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/4de9d9c261a6f2a32e98920bbc530c473b41de07"},{"sha":"115f08284df1dac6a29cbca49dc7534b4a4f23f7","author":{"name":"Sreeharsha Ramanavarapu","email":"d8d629b6f84f7a91d47bb2648eefc4386d699150@oracle.com"},"message":"Bug #23279858: MYSQLD GOT SIGNAL 11 ON SIMPLE SELECT\n               NAME_CONST QUERY\n\nISSUE:\n------\nUsing NAME_CONST with a non-constant negated expression as\nvalue can result in incorrect behavior.\n\nSOLUTION:\n---------\nThe problem can be avoided by checking whether the argument\nis a constant value.\n\nThe fix is a backport of Bug#12735545.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/115f08284df1dac6a29cbca49dc7534b4a4f23f7"},{"sha":"5dc6a77b409291140e072470673589982a6623a2","author":{"name":"Arun Kuruvila","email":"c3295ca9b7a8ae0f17233a6b9b393518a7012863@oracle.com"},"message":"Bug#23035296: MAIN.MYSQLDUMP FAILS BECUASE OF UNEXPECTED\n              ERROR MESSAGE\n\nDescription:- Mtr test, \"main.mysqldump\" is failing with an\nassert when \"mysqlimport\" client utility is executed with\nthe option \"--use_threads\".\n\nAnalysis:- \"mysqlimport\" uses the option, \"--use_threads\",\nto spawn worker threads to complete its job in parallel. But\ncurrently the main thread is not waiting for the worker\nthreads to complete its cleanup, rather just wait for the\nworker threads to say its done doing its job. So the cleanup\nis done in a race between the worker threads and the main\nthread. This lead to an assertion failure.\n\nFix:- \"my_thread_join()\" is introduced in the main thread to\njoin all the worker threads it have spawned. This will let\nthe main thread to wait for all the worker threads to\ncomplete its cleanup before calling \"my_end()\".","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/5dc6a77b409291140e072470673589982a6623a2"},{"sha":"96d90250c66d9159522582a541c87e3c9d8b8d08","author":{"name":"Arun Kuruvila","email":"c3295ca9b7a8ae0f17233a6b9b393518a7012863@oracle.com"},"message":"Bug#23035296: MAIN.MYSQLDUMP FAILS BECUASE OF UNEXPECTED\n              ERROR MESSAGE\n\nPost push patch to fix test case failure.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/96d90250c66d9159522582a541c87e3c9d8b8d08"},{"sha":"07e50c4291b3f771b3606362c05b3a6e495a3448","author":{"name":"Prashant Tekriwal","email":"36db45e51f37e700dfe9addbfb10507186cffd0c@oracle.com"},"message":"Merge branch 'mysql-5.5.50-release' into mysql-5.5","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/07e50c4291b3f771b3606362c05b3a6e495a3448"},{"sha":"df0d8efaf25a69990cf422d55011c1c0eebdec51","author":{"name":"Arun Kuruvila","email":"c3295ca9b7a8ae0f17233a6b9b393518a7012863@oracle.com"},"message":"Bug#23035296: MAIN.MYSQLDUMP FAILS BECUASE OF UNEXPECTED\n              ERROR MESSAGE\n\nPost push patch to fix test case failure.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/df0d8efaf25a69990cf422d55011c1c0eebdec51"},{"sha":"957aefdc8f5523a1d45775f5ce3de74c03f5ed98","author":{"name":"Shishir Jaiswal","email":"2826c01bafe13e56ad18d112d99a03b9dbc6e968@oracle.com"},"message":"Bug#23498283 - BUFFER OVERFLOW\n\nDESCRIPTION\n===========\nBuffer overflow is reported in Regex library. This can be\ntriggered when the data corresponding to argv[1] is >=\n512 bytes resutling in abnormal behaviour.\n\nANALYSIS\n========\nIts a straight forward case of SEGFAULT where the target\nbuffer is smaller than the source string to be copied.\nA simple pre-copy validation should do.\n\nFIX\n===\nA check is added before doing strcpy() to ensure that the\ntarget buffer is big enough to hold the to-be copied data.\nIf the check fails, the program aborts.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/957aefdc8f5523a1d45775f5ce3de74c03f5ed98"},{"sha":"4a3f1c1f104cbfeb6d31ee02788589151b131eca","author":{"name":"Terje Rosten","email":"638d39825236b454b996ddfc1ebe2914c2a0513b@oracle.com"},"message":"BUG#17903583 MYSQL-COMMUNITY-SERVER SHOULD NOT DEPEND ON MYSQL-COMMUNITY-CLIENT (#70985)\n\nFix is a backport of BUG#18518216/72230 to MySQL 5.5 and 5.6.\n\nWill also resolve:\n\n BUG#23605713/81384 LIBMYSQLCLIENT.SO.18 MISSING FROM MYSQL 5.7\n\n  as mysql-community-libs-5.5 or mysql-community-libs-5.6 can\n  installed on EL6 system with libmysqlclient.16 (from MySQL 5.1)\n  libmysqlclient.20 (from MySQL 5.7) by doing:\n\n  $ rpm --oldpackage -ivh mysql-community-libs-5.5.50-2.el6.x86_64.rpm\n\n  Providing a way to have several versions of libmysqlclient installed\n  on the same system.\n\nand help:\n\n BUG#23088014/80981 LIBS-COMPAT RPMS SHOULD BE INDEPENDENT OF ALL OTHER SUBPACKAGES\n\n  due to less strict coupling between -libs-compat and -common package.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/4a3f1c1f104cbfeb6d31ee02788589151b131eca"},{"sha":"7ff86b49912df5de7b5a8b9c9134e72134b7ba5c","author":{"name":"Vicențiu Ciorbaru","email":"50b75d5e083597d9f1b4c528efb494654b1bb549@mariadb.org"},"message":"MDEV-10247 TokuDB assertion error when building with DEBUG\n\nFix the assertion failure by setting the struct to 0. This can not be\ndone using a macro due to different definitions of mutexes on various\nOS-es.\nAfterwards we call toku_mutex_init and completely initialize the locks.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/7ff86b49912df5de7b5a8b9c9134e72134b7ba5c"},{"sha":"128930c19b4ebc6a50f254bcee6af84db79ebe91","author":{"name":"Daniel Bartholomew","email":"a12139f7c9cc1f3eb4b40ca36318a3085c27d596@dbart.us"},"message":"bump the VERSION","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/128930c19b4ebc6a50f254bcee6af84db79ebe91"},{"sha":"9f7288e2e0179db478d20c74f57b5c7d6c95f793","author":{"name":"Thayumanavar S","email":"116f8d587ee2d4058cb1c267d77640a5a83d5f07@oracle.com"},"message":"BUG#23080148 - BACKPORT BUG 14653594 AND BUG 20683959 TO\n               MYSQL-5.5\n\nThe bug asks for a backport of bug#1463594 and bug#20682959. This\nis required because of the fact that if replication is enabled, master\ntransaction can commit whereas slave can't commit due to not exact\n'enviroment'. This manifestation is seen in bug#22024200.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/9f7288e2e0179db478d20c74f57b5c7d6c95f793"},{"sha":"7f38a070baa503a37af186ff24f39606816f55ec","author":{"name":"Sergey Vojtovich","email":"f7bb3c4d1423048768491a0d16a8f7427983335b@mariadb.org"},"message":"MDEV-10043 - main.events_restart fails sporadically in buildbot (crashes upon\n             shutdown)\n\nThere was race condition between shutdown thread and event worker threads.\n\nShutdown thread waits for thread_count to become 0 in close_connections(). It\nmay happen so that event worker thread was started but didn't increment\nthread_count by this time. In this case shutdown thread may miss wait for this\nworking thread and continue deinitialization. Worker thread in turn may continue\nexecution and crash on deinitialized data.\n\nFixed by incrementing thread_count before thread is actually created like it is\ndone for connection threads.\n\nAlso let event scheduler not to inc/dec running threads counter for symmetry\nwith other \"service\" threads.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/7f38a070baa503a37af186ff24f39606816f55ec"},{"sha":"95bf696d2c8ee189a1836b5b0e4ec353aa4bda30","author":{"name":"Sergei Golubchik","email":"6e25d0b739c1a159a12a5fefc96fcf208fd10801@mariadb.org"},"message":"MDEV-9749 InnoDB receives 'Bad file descriptor' error, possibly related to feedback plugin\n\nand\nMDEV-10250 InnoDB: Error: File (unknown): 'close' returned OS error 209. Cannot continue operation\"\n\nafter a failed connect() feedback plugin was continuing with the\nfile descriptor, trying to send the data (which failed) and\nclosing it at the end. Even though this fd might've been reused for\nsomething else already.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/95bf696d2c8ee189a1836b5b0e4ec353aa4bda30"},{"sha":"a482e76e65a4fee70479e877929381c86b1ec62f","author":{"name":"Sergei Golubchik","email":"6e25d0b739c1a159a12a5fefc96fcf208fd10801@mariadb.org"},"message":"fix a mysql-5.5.50 merge: mysqlcheck\n\nquote identifiers correctly","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/a482e76e65a4fee70479e877929381c86b1ec62f"}]}
{"actor":{"display_login":"nirbhayc"}}