mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-17 12:32:27 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
186738 commits 2784 branches 343 tags 1.6 GiB
MariaDB\ 71.8%
C++ 16.2%
C 10.6%
Shell 0.5%
Perl 0.4%
Other 0.3%
Find a file
Marko Mäkelä ae1d17f52d MDEV-20316 InnoDB writes uninitialised tail of XID buffer 
Starting with commit 210855ce5d
Valgrind became aware that the unused tail of the buffer that
is returned by thd_get_xid() is actually uninitialized.

The problem should exist already in MySQL 5.0. I was able to
repeat it on MariaDB Server 5.5 with some additional instrumentation.
InnoDB is allocating 128+4+4 bytes for the XID and the lengths of
its components, even when the XID is shorter than 64+64 bytes.
In MariaDB Server 10.3, while running the test main.xa_binlog,
in the xid_t::set() that is called by sql_yacc.yy, the 128-byte data
buffer was uninitialized according to Valgrind, and only the first bytes
were initialized. When the xid_t::data was copied to
thd.transaction.xid_state.xid.data, it happened so that the entire
target buffer was considered initialized. With MariaDB Server 10.4 since
the said commit, Valgrind will correctly be detect the tail of the buffer
as uninitialized.

The impact of this bug is as follows:

(1) InnoDB will write unnecessarily much redo log for XA PREPARE.
(2) InnoDB will write garbage bytes to the redo log and undo log pages.
(3) The garbage should be 'harmless', because on recovery, only the
actual payload of the XID will be used, based on the written length.

trx_rseg_write_wsrep_checkpoint(), trx_undo_write_xid(): Write only
the actually used length of xid->data to the data page, and
zero out the rest of the buffer by mlog_memset().
2019-08-12 19:37:24 +03:00
BUILD Merge 10.3 into 10.4 2019-06-19 10:49:00 +03:00
client Merge 10.3 into 10.4 2019-07-25 18:42:06 +03:00
cmake Merge 10.3 into 10.4 2019-07-25 18:42:06 +03:00
dbug Merge 10.2 into 10.3 2019-05-14 17:18:46 +03:00
debian Merge 10.3 into 10.4 2019-07-25 18:42:06 +03:00
Docs Merge branch '10.3' into 10.4 2019-06-14 22:10:50 +02:00
extra Do not compile socket IO code in WolfSSL 2019-07-28 13:45:34 +02:00
include Fixed that mariadb-# binaries reads their corresponding entry from my.cnf 2019-07-18 15:32:22 +03:00
libmariadb@ed3a91c139 Merge branch '10.1' into 10.2 2019-07-26 07:03:39 +02:00
libmysqld Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
libservices Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
man MDEV-19847: Update mysqladmin man page 2019-07-01 12:09:40 +04:00
mysql-test MDEV-19301 Assertion `!is_valid_datetime() || fraction_remainder(((item->decimals) < (6) ? (item->decimals) : (6))) == 0' failed in Datetime_truncation_not_needed::Datetime_truncation_not_needed 2019-08-06 10:53:55 +04:00
mysys Merge 10.3 into 10.4 2019-07-26 15:22:31 +03:00
mysys_ssl Update WolfSSL, remove older workarounds. 2019-07-28 13:45:15 +02:00
pcre Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
plugin Fixes based on warnings from gcc/clang and valgrind 2019-08-12 10:48:38 +03:00
randgen/conf
scripts Merge branch '10.3' into 10.4 2019-07-28 13:43:26 +02:00
sql Revert part of 05619f6989 2019-08-12 19:37:24 +03:00
sql-bench Merge 10.2 into 10.3 2019-05-14 17:18:46 +03:00
sql-common MDEV-19301 Assertion `!is_valid_datetime() || fraction_remainder(((item->decimals) < (6) ? (item->decimals) : (6))) == 0' failed in Datetime_truncation_not_needed::Datetime_truncation_not_needed 2019-08-06 10:53:55 +04:00
storage MDEV-20316 InnoDB writes uninitialised tail of XID buffer 2019-08-12 19:37:24 +03:00
strings Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
support-files Merge branch '10.3' into 10.4 2019-07-28 13:43:26 +02:00
tests MDEV-17592 Create MariaDB named commands/symlinks 2019-06-17 12:26:26 +02:00
unittest Merge 10.3 into 10.4 2019-06-12 08:37:27 +03:00
vio Do not compile socket IO code in WolfSSL 2019-07-28 13:45:34 +02:00
win Merge branch '10.3' into 10.4 2019-07-28 13:43:26 +02:00
wsrep-lib@0f676bd893 - wsrep-lib update (SR cleanups and voting support) (#1359) 2019-07-22 16:34:12 +03:00
zlib Merge 10.1 into 10.2 2019-07-18 13:10:09 +03:00
.clang-format MDEV-13631 Make use of clang-format 2019-06-12 22:36:43 +03:00
.gitattributes Merge branch '10.0' into 10.1 2018-05-05 14:01:59 +02:00
.gitignore wsrep_check_version binary is added to .gitignore 2019-07-18 15:11:32 +02:00
.gitmodules Fix github urls of submodules 2019-07-02 17:25:36 +04:00
.travis.compiler.sh travis: use galera-4 in 10.4 branch (#1226) 2019-03-14 08:20:32 +02:00
.travis.yml travis: use galera-4 in 10.4 branch (#1226) 2019-03-14 08:20:32 +02:00
appveyor.yml Appveyor configuration and addition of badge 2019-01-10 11:58:02 +01:00
BUILD-CMAKE Minor spelling fixes in code comments, docs and output 2018-01-12 16:49:02 +02:00
CMakeLists.txt Merge 10.3 into 10.4 2019-07-25 18:42:06 +03:00
config.h.cmake MDEV-19696 - Cleanup gcc sync builtins 2019-07-03 12:11:22 +03:00
configure.cmake MDEV-19696 - Cleanup gcc sync builtins 2019-07-03 12:11:22 +03:00
CONTRIBUTING.md Add CONTRIBUTING file and modify README file about live QA regarding new contributors 2018-12-04 23:15:33 +04:00
COPYING Update FSF Address 2019-05-11 21:29:06 +03:00
CREDITS Update contributors 2018-09-10 16:47:44 +04:00
EXCEPTIONS-CLIENT MDEV-5645 MariaDB-5.5.35 - references are made to an "EXCEPTIONS-CLIENT" file but it does not exist 2014-05-31 13:18:56 +02:00
INSTALL-SOURCE Update AskMonty and Atlassian references to MariaDB 2016-03-08 15:24:01 +02:00
INSTALL-WIN-SOURCE Update AskMonty and Atlassian references to MariaDB 2016-03-08 15:24:01 +02:00
KNOWN_BUGS.txt Changed some MySQL names in messages to MariaDB 2018-12-09 20:49:05 +02:00
README.md Merge branch '10.3' into 10.4 2019-05-19 20:55:37 +02:00
THIRDPARTY Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
VERSION bump the VERSION 2019-07-31 10:00:26 -04:00

README.md

Code status:

  • Travis CI status travis-ci.org (10.4 branch)
  • Appveyor CI status ci.appveyor.com

MariaDB: drop-in replacement for MySQL

MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

MariaDB is brought to you by the MariaDB Foundation and the MariaDB corporation. Please read the CREDITS file for details about the MariaDB Foundation, and who is developing MariaDB.

MariaDB is developed by many of the original developers of MySQL who now work for the MariaDB Corporation, the MariaDB Foundation and by many people in the community.

MySQL, which is the base of MariaDB, is a product and trademark of Oracle Corporation, Inc. For a list of developers and other contributors, see the Credits appendix. You can also run 'SHOW authors' to get a list of active contributors.

A description of the MariaDB project and a manual can be found at:

https://mariadb.com/kb/en/

https://mariadb.com/kb/en/mariadb-vs-mysql-features/

https://mariadb.com/kb/en/mariadb-versus-mysql-compatibility/

https://mariadb.com/kb/en/library/new-and-old-releases/

https://mariadb.org/

As MariaDB is a full replacement of MySQL, the MySQL manual at http://dev.mysql.com/doc is generally applicable.

Help

More help is available from the Maria Discuss mailing list https://launchpad.net/~maria-discuss and the #maria IRC channel on Freenode.

Live QA for beginner contributors

MariaDB has a dedicated time each week when we answer new contributor questions live on Zulip and IRC. From 8:00 to 10:00 UTC on Mondays, and 10:00 to 12:00 UTC on Thursdays, anyone can ask any questions they’d like, and a live developer will be available to assist.

New contributors can ask questions any time, but we will provide immediate feedback during that interval.

Licensing

NOTE:

MariaDB is specifically available only under version 2 of the GNU General Public License (GPLv2). (I.e. Without the "any later version" clause.) This is inherited from MySQL. Please see the README file in the MySQL distribution for more information.

License information can be found in the COPYING file. Third party license information can be found in the THIRDPARTY file.

Bug Reports

Bug and/or error reports regarding MariaDB should be submitted at: https://jira.mariadb.org

For reporting security vulnerabilities see: https://mariadb.org/about/security-policy/

Bugs in the MySQL code can also be submitted at: https://bugs.mysql.com

The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server