linux-kernel - simultaneous signal handling and setjmp/longjmp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 06 Nov 2009 17:09:50 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	linux-kernel@...r.kernel.org
Subject: simultaneous signal handling and setjmp/longjmp

I've got a bit of an odd hypothetical question dealing with signals and
setjmp/longjmp.

Suppose we have an app with multiple signals pending.  (Say, SIGALRM and
SIGSEGV.)  In the signal handler for SIGSEGV, we're going to call call
longjmp().  (Yes, I'm aware of the issues.)

At this point we're still in the kernel and both SIGSEGV and SIGALARM
are pending. What happens?

If we run the SIGSEGV handler does the SIGALARM stay pending until the
segfault handler completes?  What happens when the segfault handler
calls longjmp()?  Does the SIGALARM handler get called on the logical
return from sigsetjmp(), and if so how does that happen since the glibc
code for setjmp/longjmp doesn't seem to call any kernel syscalls?

Thanks for any information you can provide...

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/