sandbox: don't set SA_NODEFER in signal handler

The sandbox can handle signals. Due to a damaged global data pointer
additional exceptions in the signal handler may occur leading to an endless
loop. In this case leave the handling of the secondary exception to the
operating system.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>

diff --git a/arch/sandbox/cpu/os.c b/arch/sandbox/cpu/os.c
index a8aa9def27f2c9bd82eabc143d5e106e4f665b25..1103530941b3b4c8016d8c9018c7574ee3e7b603 100644 (file)
--- a/arch/sandbox/cpu/os.c
+++ b/arch/sandbox/cpu/os.c
@@ -226,7 +226,7 @@ int os_setup_signal_handlers(void)
 
        act.sa_sigaction = os_signal_handler;
        sigemptyset(&act.sa_mask);
-       act.sa_flags = SA_SIGINFO | SA_NODEFER;
+       act.sa_flags = SA_SIGINFO;
        if (sigaction(SIGILL, &act, NULL) ||
            sigaction(SIGBUS, &act, NULL) ||
            sigaction(SIGSEGV, &act, NULL))