diff options
author | H. Peter Anvin <hpa@linux.intel.com> | 2009-01-14 11:28:35 -0800 |
---|---|---|
committer | H. Peter Anvin <hpa@linux.intel.com> | 2009-01-14 11:28:35 -0800 |
commit | 73310a169aebe257efdd35a763cce1c7658f40c9 (patch) | |
tree | 4195dba6ed5c20fafc4d790167600433841f125e /Documentation/x86/boot.txt | |
parent | 23a22d57a8962479ca630c9542e62d6f86fdf927 (diff) | |
download | kernel-crypto-73310a169aebe257efdd35a763cce1c7658f40c9.tar.gz kernel-crypto-73310a169aebe257efdd35a763cce1c7658f40c9.tar.xz kernel-crypto-73310a169aebe257efdd35a763cce1c7658f40c9.zip |
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 'Documentation/x86/boot.txt')
0 files changed, 0 insertions, 0 deletions