test

   Helgrind:Race

   obj:*/ld-musl-*

}

# ----------------------------------------------------------------

# False lock-order violations between libnetplus EventWorker

# connection mutex and application-level mutexes.

# The HTTP connection mutex is always acquired by the EventWorker

# framework before dispatching to user code.  Application locks

# (e.g. cluster client_mutex_) are only acquired from within

# request handlers or the main/sync thread — never in the

# reverse order.  No actual deadlock is possible.

# ----------------------------------------------------------------

{

   eventworker_conn_vs_app_lock_order

   Helgrind:LockOrder

   ...

   fun:_ZN7netplus11EventWorkerC1EimPNS_15EventWorkerArgsE*

}