Skip to content
Sign in
Success

#20830 (Mar 9, 2026, 11:44:30 AM)

Started 9 hr 44 min ago
Took 4 min 11 sec on build5-deb12build-ansible

Started by upstream project gerrit-osmo-remsim build number 121
originally caused by:

This run spent:

  • 10 sec waiting;
  • 4 min 11 sec build duration;
  • 4 min 21 sec total from scheduled to completion.
Revision: 209c015fac6ee39b2f4dac6dec2423da98decb21
Repository: $GERRIT_REPO_URL
  • master
bankd: Avoid osmocom logging mutex deadlock in signal handling

The main thread communicates slotmap add + delete via POSIX signals
to the worker threads.  As those signals interrupt the normal
processing of the worker thread, they might get delivered while the
thread is already logging something, causing a deadlock.  This has
been observed in the real world in the following stack trace (where it's
actually two nested signals):

As a hot-fix, let's avoid logging from the handle_sig_map{del,add}()
functions at all, making them safe against a deadlock around this mutex.

We should decide how to proceed in general with potentially some
architectural changes later on; any such changes are not suitable as a
hot fix due to their potential of introducing other regressions.

Change-Id: I5ea32886dfaf624b4dc5ad7924941c7b904c1d36
Related: SYS#7930
laforge at