From ed51a172c69996fc6f3b7dfaa86015bff50c8ba8 Mon Sep 17 00:00:00 2001 From: Yureka Date: Tue, 20 Aug 2024 09:09:57 +0200 Subject: [PATCH] libutil: fix conditional for close_range availability This check is wrong and would cause the close_range() function being called even when it's not available Change-Id: Ide65b36830e705fe772196c37349873353622761 (cherry picked from commit df49d37b71e1a4bcb3ba9c567a6f8f5a07cba39a) --- src/libutil/file-descriptor.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/libutil/file-descriptor.cc b/src/libutil/file-descriptor.cc index f95d7b321..8385ea402 100644 --- a/src/libutil/file-descriptor.cc +++ b/src/libutil/file-descriptor.cc @@ -228,7 +228,7 @@ void closeExtraFDs() auto closeRange = [](unsigned int first, unsigned int last, int flags) -> int { // musl does not have close_range as of 2024-08-10 // patch: https://www.openwall.com/lists/musl/2024/08/01/9 -#ifdef HAVE_CLOSE_RANGE +#if HAVE_CLOSE_RANGE return close_range(first, last, flags); #else return syscall(SYS_close_range, first, last, flags);