tree b800f241f3d49dce3ef79c7ec2e6cf8ff04e07a7
parent 63843c265fd0e0c7894f713e0db5777560e756ae
author Jeff Dike <jdike@addtoit.com> 1178488300 -0700
committer Linus Torvalds <torvalds@woody.linux-foundation.org> 1178565183 -0700

uml: don't try to handle signals on initial process stack

Code running on the initial UML stack can't receive or process signals since
current must be valid when IRQs are handled, and there is no current for this
stack.

So, instead of using UML_LONGJMP and UML_SETJMP, which are careful to save and
restore signal state, and, as a side-effect, handle any deferred signals,
start_idle_thread must use the bare equivalents, which don't do anything with
signals.

Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>