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
This commit is contained in:
parent
e727dbc3a3
commit
df49d37b71
1 changed files with 1 additions and 1 deletions
|
@ -228,7 +228,7 @@ void closeExtraFDs()
|
||||||
auto closeRange = [](unsigned int first, unsigned int last, int flags) -> int {
|
auto closeRange = [](unsigned int first, unsigned int last, int flags) -> int {
|
||||||
// musl does not have close_range as of 2024-08-10
|
// musl does not have close_range as of 2024-08-10
|
||||||
// patch: https://www.openwall.com/lists/musl/2024/08/01/9
|
// 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);
|
return close_range(first, last, flags);
|
||||||
#else
|
#else
|
||||||
return syscall(SYS_close_range, first, last, flags);
|
return syscall(SYS_close_range, first, last, flags);
|
||||||
|
|
Loading…
Reference in a new issue