From 8c1f93bf84b24591b783375c881c1effca3e9db0 Mon Sep 17 00:00:00 2001
From: Nikolay Shirokovskiy <nshirokovskiy@tarantool.org>
Date: Mon, 19 Jun 2023 14:08:44 +0300
Subject: [PATCH] fiber: don't unpoison fiber stack
The unpoison was added in the initial commit 1.7.2-68-gafd229393 that
supported ASAN. It is not clear why do we need it as we don't poison
stack memory manually.
Part of #7327
NO_TEST=removing unfunctional code
NO_CHANGELOG=removing unfunctional code
NO_DOC=removing unfunctional code
(cherry picked from commit 0784f7b71d25c615e2313e7b00de78df4399c8a3)
---
src/lib/core/fiber.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/src/lib/core/fiber.c b/src/lib/core/fiber.c
index d634f7641c..6e03dc7fca 100644
--- a/src/lib/core/fiber.c
+++ b/src/lib/core/fiber.c
@@ -1289,9 +1289,6 @@ fiber_stack_destroy(struct fiber *fiber, struct slab_cache *slabc)
if (fiber->stack != NULL) {
VALGRIND_STACK_DEREGISTER(fiber->stack_id);
-#if ENABLE_ASAN
- ASAN_UNPOISON_MEMORY_REGION(fiber->stack, fiber->stack_size);
-#endif
void *guard;
if (stack_direction < 0)
guard = page_align_down(fiber->stack - page_size);
--
GitLab