um: don't bother blocking SIGARLM and SIGUSR1

We used to generate those, but we hadn't done that for a long
time.  No need to bother blocking them for signal handlers.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Richard Weinberger <richard@nod.at>

1 files changed, 1 insertions, 1 deletions

diff --git a/arch/um/os-Linux/skas/process.c b/arch/um/os-Linux/skas/process.c
index f481d745e231..20b34dcb0906 100644
--- a/arch/um/os-Linux/skas/process.c
+++ b/arch/um/os-Linux/skas/process.c
@@ -660,7 +660,7 @@ int start_idle_thread(void *stack, jmp_buf *switch_buf)
         int n;
 
         set_handler(SIGWINCH, (__sighandler_t) sig_handler,
-                    SA_ONSTACK | SA_RESTART, SIGUSR1, SIGIO, SIGVTALRM, -1);
+                    SA_ONSTACK | SA_RESTART, SIGIO, SIGVTALRM, -1);
 
         /*
          * Can't use UML_SETJMP or UML_LONGJMP here because they save