Incorrect POSIX_SPAWN_SETSIGDEF usage in wsrep_utils.cc

[Alexey Kopytov]

The code in the wsp::process class constructor uses posix_spawn() to create a child process. In particular, it sets the POSIX_SPAWN_SETSIGDEF flag via posix_spawnattr_setflags():

   err_ = posix_spawnattr_setflags (&attr, POSIX_SPAWN_SETSIGDEF |
                                           POSIX_SPAWN_USEVFORK);

The goal was apparently to reset the ignored (SIG_IGN) state set by the server for certain signals (e.g. SIGINT) back to their default handlers.

However, the POSIX_SPAWN_SETSIGDEF flag only makes sense when used together with a posix_spawnattr_setsigdefault() call, otherwise it has no effect because it will apply to an empty signal set. Quoting http://linux.die.net/man/3/posix_spawnattr_setsigdefault :

"
The spawn-sigdefault attribute represents the set of signals to be forced to default signal handling in the new process image (if POSIX_SPAWN_SETSIGDEF is set in the spawn-flags attribute) by a spawn operation. The default value of this attribute shall be an empty signal set.
"

As a result, the SST process spawn code does not reset any ignored signals as intended.

[Alexey Kopytov (akopytov)]

This will be fixed in 5.6 with the patch for bug #1382797. As a side effect, because all code related to the posix_spawn*() family of functions will be replaced.

[Alexey Kopytov (akopytov)]

On a second thought, this bug will also be fixed in PXC 5.5.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1148