[debian-mysql] Bug#832931: jemalloc hard codes page size during build

Thadeu Lima de Souza Cascardo cascardo at debian.org
Thu Nov 10 18:37:20 UTC 2016


clone -1 -2
reassign -2 libjemalloc1
retitle -2 jemalloc uses a hard coded page size detected during build
bye


So, I traced this to jemalloc using the incorrect page size during
runtime. In fact, it detects the page size during build and set it up.
This has a large potential for a mess. And what a mess!

So, jemalloc in jessie has been built on a 4KiB-page system, and, this,
has a hard-coded page size of 4KiB. While jemalloc in sid has a
64KiB-page size. When we try to build mariadb on jessie on a 4KiB-page
size system, everything goes well. When we build it on partch, with a
64-bit 64KiB-page size kernel, things break, if it's a jessie jemalloc.

Later upstream versions seem to support multiple page sizes during
build.

For MariaDB specifically, one option would be to build it without
jemalloc. Other users would still be likely affected, however.

Cascardo.



More information about the pkg-mysql-maint mailing list