summaryrefslogtreecommitdiff
path: root/storage/innobase/buf/buf0buf.cc
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-07-05 16:31:34 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2020-07-05 16:31:34 +0300
commitf3f23b5c4bdc669ad0af4a1c79bd70c40ed9c594 (patch)
tree1fe63afb7dcdb15032d7eb680aaf39fd41257176 /storage/innobase/buf/buf0buf.cc
parent453dc4b300e0d595adb736fb555e62a42accfa2b (diff)
downloadmariadb-git-f3f23b5c4bdc669ad0af4a1c79bd70c40ed9c594.tar.gz
One more ASAN/MSAN cleanup
commit 484931325e7bcecddc6daf1a55c008ddd67497e4 included a workaround for a 10.5 merge issue that should now be properly addressed in commit ab4069909d1f8d0c4740b5bd90e1422ce1978187. buf_chunk_init(): Remove an unnecessary MEM_MAKE_ADDRESSABLE(). We might invoke MEM_UNDEFINED() here, but actually the allocated memory ought to be guaranteed to be zero-initialized.
Diffstat (limited to 'storage/innobase/buf/buf0buf.cc')
-rw-r--r--storage/innobase/buf/buf0buf.cc2
1 files changed, 0 insertions, 2 deletions
diff --git a/storage/innobase/buf/buf0buf.cc b/storage/innobase/buf/buf0buf.cc
index f2594725391..88c4c7ba7fd 100644
--- a/storage/innobase/buf/buf0buf.cc
+++ b/storage/innobase/buf/buf0buf.cc
@@ -1622,8 +1622,6 @@ buf_chunk_init(
return(NULL);
}
- MEM_MAKE_ADDRESSABLE(chunk->mem, chunk->mem_size());
-
#ifdef HAVE_LIBNUMA
if (srv_numa_interleave) {
struct bitmask *numa_mems_allowed = numa_get_mems_allowed();