monkburger opened a new pull request #34:
URL: https://github.com/apache/apr/pull/34
Under specific circumstances, apr_global_mutex_child_init can be called with
NULL mutex. We've seen this behavior under certain modules, specifically
mod_lsapi and a few others under high load/IO wait during graceful restarts:
```
#0 apr_proc_mutex_child_init (mutex=0x8, fname=0x0, pool=0x5566e972f128)
at locks/unix/proc_mutex.c:1570
#1 0x00002b9a5730cd2c in apr_global_mutex_child_init (mutex=<optimized
out>, fname=<optimized out>, pool=<optimized out>) at
locks/unix/global_mutex.c:89
```
With this patch, it shows the following - as well as no more segfaults:
[Fri Feb 25 01:13:58.924341 2022] [:emerg] [pid 92020] (20009)No lock was
provided and one was required.: [host test.test] mod_lsapi:
apr_global_mutex_child_init error for pipe mutex
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@apr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
