Skip to contentSkip to conversation

test-lib.sh: Use GLIBC_TUNABLES instead of MALLOC_CHECK_ on glibc >= 2.34

PATCH Superseded Elia Pinto 2 participants 2 messages Mar 3, 2022

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Elia Pinto

author
#0 lore raw

PATCH v2 1/1 test-lib.sh: Use GLIBC_TUNABLES instead of MALLOC_CHECK_ on glibc >= 2.34

In glibc >= 2.34 MALLOC_CHECK_ and MALLOC_PERTURB_ environment variables have been replaced by GLIBC_TUNABLES. Also the new glibc requires that you preload a library called libc_malloc_debug.so to get these features.

Using the ordinary glibc system variable detect if this is glibc >= 2.34 and use GLIBC_TUNABLES and the new library.

This patch was inspired by a Richard W.M. Jones ndbkit patch

---
This is the second version of the patch.

Compared to the first version, the code has been simplified, based on Junio's indications, introducing some redundancy in the setting of the glibc variables covered by the patch
(https://lore.kernel.org/all/[email protected]/)

 t/test-lib.sh | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
t/test-lib.sh +21 -0
index 9af5fb7674..b545013a14 100644
@@ -548,11 +548,32 @@ then
 	}
 else
 	setup_malloc_check () {
+		if _GLIBC_VERSION=$(getconf GNU_LIBC_VERSION 2>/dev/null) &&
+		_GLIBC_VERSION=${_GLIBC_VERSION#"glibc "} &&
+		expr 2.34 \<= "$_GLIBC_VERSION" >/dev/null
+		then
+			USE_GLIBC_TUNABLES=YesPlease
+		fi
 		MALLOC_CHECK_=3	MALLOC_PERTURB_=165
 		export MALLOC_CHECK_ MALLOC_PERTURB_
+		case "$USE_GLIBC_TUNABLES" in
+		YesPlease)
+			g=
+			LD_PRELOAD="libc_malloc_debug.so.0"
+			for t in \
+				glibc.malloc.check=1 \
+				glibc.malloc.perturb=165
+			do
+				g="${g##:}:$t"
+			done
+			GLIBC_TUNABLES=$g
+			export LD_PRELOAD GLIBC_TUNABLES
+			;;
+		esac
 	}
 	teardown_malloc_check () {
 		unset MALLOC_CHECK_ MALLOC_PERTURB_
+		unset LD_PRELOAD GLIBC_TUNABLES
 	}
 fi
 
Signature · 1 line
2.35.1
#1 lore raw
Quoted 3 lines · Elia Pinto

Compared to the first version, the code has been simplified, based on Junio's indications, introducing some redundancy in the setting of the glibc variables covered by the patch

I think we can even lose the separate case statement and write its body inside if/then...fi. The following shows the result of shuffling the lines to do so.

t/test-lib.sh then · line 553

Quoted 4 lines
t/test-lib.sh +3 -0
 	setup_malloc_check () {
+		if _GLIBC_VERSION=$(getconf GNU_LIBC_VERSION 2>/dev/null) &&
+		   _GLIBC_VERSION=${_GLIBC_VERSION#"glibc "} &&
+		   expr 2.34 \<= "$_GLIBC_VERSION" >/dev/null

I am wondering if we want to make sure "getconf" returned a string that begins with "glibc " before stripping that prefix. Hopefully such a paranoia is probably unneeded.

t/test-lib.sh then · line 567

Quoted 8 lines
t/test-lib.sh +8 -0
+		then
+			g=
+			LD_PRELOAD="libc_malloc_debug.so.0"
+			for t in \
+				glibc.malloc.check=1 \
+				glibc.malloc.perturb=165
+			do
+				g="${g##:}:$t"

Cute. As this strips a constant, we do not need to be ##greedy and using just a single # would suffice, right?

t/test-lib.sh then · line 578

Quoted 13 lines
t/test-lib.sh +6 -0
+			done
+			GLIBC_TUNABLES=$g
+			export LD_PRELOAD GLIBC_TUNABLES
+			;;
+		fi
 		MALLOC_CHECK_=3	MALLOC_PERTURB_=165
 		export MALLOC_CHECK_ MALLOC_PERTURB_
 	}
 	teardown_malloc_check () {
 		unset MALLOC_CHECK_ MALLOC_PERTURB_
+		unset LD_PRELOAD GLIBC_TUNABLES
 	}
 fi

especially the teardown side unsets these unconditionally.