Actions
Bug #2360
closedpossible deadlock with signal handling
Affected Versions:
Effort:
Difficulty:
Label:
Description
I got a bug report about signal handling and a possible deadlock that needs investigation:
Send SIGHUP and some time after SIGUSR2. This results in rotation_flag being set. With the rule reload the rule reload starting message is generated. In SCLogMessage the op_iface_ctx->fp_mutex becomes locked. But since the rotation_flag is set we call SCLogReopen which triggers another SCLogMessage when it doesn't have the proper permissions at that point. This results in a recursion in the scenario, since the flag is released AFTER the reopen.
Updated by Victor Julien about 7 years ago
- Related to Bug #2306: suricata 4 deadlocks during failed output log reopening added
Updated by Victor Julien about 7 years ago
- Status changed from New to Closed
- Assignee changed from OISF Dev to Victor Julien
- Target version changed from TBD to 4.1beta1
Actions