aboutsummaryrefslogtreecommitdiff
path: root/init/do_mounts_rd.c
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@linux.intel.com>2009-01-14 11:28:35 -0800
committerH. Peter Anvin <hpa@linux.intel.com>2009-01-14 11:28:35 -0800
commit73310a169aebe257efdd35a763cce1c7658f40c9 (patch)
tree4195dba6ed5c20fafc4d790167600433841f125e /init/do_mounts_rd.c
parent23a22d57a8962479ca630c9542e62d6f86fdf927 (diff)
downloadlinux-linaro-stable-73310a169aebe257efdd35a763cce1c7658f40c9.tar.gz
init: make initrd/initramfs decompression failure a KERN_EMERG event
Impact: More consistent behaviour, avoid policy in the kernel Upgrade/downgrade initrd/initramfs decompression failure from inconsistently a panic or a KERN_ALERT message to a KERN_EMERG event. It is, however, possible do design a system which can recover from this (using the kernel builtin code and/or the internal initramfs), which means this is policy, not a technical necessity. A good way to handle this would be to have a panic-level=X option, to force a panic on a printk above a certain level. That is a separate patch, however. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'init/do_mounts_rd.c')
-rw-r--r--init/do_mounts_rd.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/init/do_mounts_rd.c b/init/do_mounts_rd.c
index 91d0cfca5071..027a402708de 100644
--- a/init/do_mounts_rd.c
+++ b/init/do_mounts_rd.c
@@ -83,7 +83,8 @@ identify_ramdisk_image(int fd, int start_block, decompress_fn *decompressor)
printk(KERN_NOTICE "RAMDISK: %s image found at block %d\n",
compress_name, start_block);
if (!*decompressor)
- printk(KERN_CRIT "RAMDISK: %s decompressor not configured!\n",
+ printk(KERN_EMERG
+ "RAMDISK: %s decompressor not configured!\n",
compress_name);
nblocks = 0;
goto done;