Am 04.11.2016 um 22:08 schrieb Richard Henderson:
No, it was less specific than that. Something like "unpacking failed: error".
>And, apparently, it used to be handled with a panic() call, but then that
>was deemed "policy", and downgraded to a KERN_EMERG message:
Ouch. A silly decision, but definitely an uphill fight to get it changed.
using a big(~370MB) initrd.cpio with not enough ram (1GB) in qemu i get
this kernel message
"Initramfs unpacking failed: write error"
using a small(~14MB) initrd.cpio with just a staticaly linked c based
init for the kernel also with 1GB ram (more then enough) gives me this
kernel message:
"Initramfs unpacking failed: junk in compressed archive"
and i currently can't say if only the first is evil or both
both cpios created with "find . | cpio -H newc -o initrd.cpio"
