Commit 5c1f33e2 authored by Johannes Berg's avatar Johannes Berg Committed by Richard Weinberger
Browse files

um: Don't trace irqflags during shutdown



In the main() code, we eventually enable signals just before
exec() or exit(), in order to to not have signals pending and
delivered *after* the exec().

I've observed SIGSEGV loops at this point, and the reason seems
to be the irqflags tracing; this makes sense as the kernel is
no longer really functional at this point. Since there's really
no reason to use unblock_signals_trace() here (I had just done
a global search & replace), use the plain unblock_signals() in
this case to avoid going into the no longer functional kernel.

Fixes: 0dafcbe1 ("um: Implement TRACE_IRQFLAGS_SUPPORT")
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
Signed-off-by: default avatarRichard Weinberger <richard@nod.at>
parent e472c64a
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -170,7 +170,7 @@ int __init main(int argc, char **argv, char **envp)
	 * that they won't be delivered after the exec, when
	 * they are definitely not expected.
	 */
	unblock_signals_trace();
	unblock_signals();

	os_info("\n");
	/* Reboot */