diff options
| author | Maria Matejka <mq@ucw.cz> | 2019-10-04 12:20:02 +0200 |
|---|---|---|
| committer | Maria Matejka <mq@jmq.cz> | 2019-10-04 20:52:07 +0200 |
| commit | 24493e9169d3058958ab3ec4d2b02c5753954981 (patch) | |
| tree | c50c972dc4b0362ca77d9887ddc93a3372036653 /sysdep/unix/main.c | |
| parent | 4821251ebb13c05e8752f6f54b8e5ad6d87fecaa (diff) | |
Fixed undefined behavior on signals.
The C11 specification allows only sig_atomic_t and _Atomic variable
access. All other accesses to global variables are undefined behavior.
Using int was probably OK on x86 and x86_64; yet there were some reports
from other architectures (especially some MIPS) that in rare cases,
after issuing SIGHUP, BIRD did strange things.
Diffstat (limited to 'sysdep/unix/main.c')
| -rw-r--r-- | sysdep/unix/main.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/sysdep/unix/main.c b/sysdep/unix/main.c index db848033..a52ae3ca 100644 --- a/sysdep/unix/main.c +++ b/sysdep/unix/main.c @@ -601,9 +601,9 @@ cmd_graceful_restart(void) * Signals */ -volatile int async_config_flag; -volatile int async_dump_flag; -volatile int async_shutdown_flag; +volatile sig_atomic_t async_config_flag; +volatile sig_atomic_t async_dump_flag; +volatile sig_atomic_t async_shutdown_flag; static void handle_sighup(int sig UNUSED) |