summaryrefslogtreecommitdiffstats
path: root/arch/um/os-Linux/signal.c
diff options
context:
space:
mode:
authorJeff Dike2008-02-05 07:31:08 +0100
committerLinus Torvalds2008-02-05 18:44:29 +0100
commit0983a88b9f0ceffb2116ce92c7b273ce2aec7b93 (patch)
treecf63f0646f64eecc80e5e3cd8d9c16252a751d8e /arch/um/os-Linux/signal.c
parentuml: eliminate setjmp_wrapper (diff)
downloadkernel-qcow2-linux-0983a88b9f0ceffb2116ce92c7b273ce2aec7b93.tar.gz
kernel-qcow2-linux-0983a88b9f0ceffb2116ce92c7b273ce2aec7b93.tar.xz
kernel-qcow2-linux-0983a88b9f0ceffb2116ce92c7b273ce2aec7b93.zip
uml: install panic notifier earlier
It turns out that if there's a panic early enough, UML will just sit there in the LED-blinking loop because the panic notifier hadn't been installed yet. This patch installs it earlier. It also fixes the problem which exposed the hang, namely that if you give UML a zero-sized initrd, it will ask alloc_bootmem for zero bytes, and that will cause the panic. While I was in initrd.c, I gave it a style makeover. Prompted by checkpatch, I moved a couple extern declarations of uml_exitcode to kern_util.h. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/um/os-Linux/signal.c')
0 files changed, 0 insertions, 0 deletions