search for: find_cpio_data

AFAICT our current version does not correspond to any version in the Linux history. This commit resynchronised to the state in Linux commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. Differences from upstream: find_cpio_data is __init, printk instead of pr_*. This appears to fix Debian bug #785187. "Appears" because my test box happens to be AMD and the issue is that the (valid) cpio generated by the Intel ucode is not liked by the old Xen code. I've tested by hacking the hypervisor to look for the Intel...

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

...On 01.07.15 at 16:43, <ian.campbell at citrix.com> wrote: > AFAICT our current version does not correspond to any version in the > Linux history. This commit resynchronised to the state in Linux > commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. > > Differences from upstream: find_cpio_data is __init, printk instead of > pr_*. > > This appears to fix Debian bug #785187. "Appears" because my test box > happens to be AMD and the issue is that the (valid) cpio generated by > the Intel ucode is not liked by the old Xen code. I've tested by > hacking the hy...