linux-kernel - Re: SH4 - Cannot make initramfs work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9e0cf0bf0804050921x46dd7c8dg80dc5b6da024426d@mail.gmail.com>
Date:	Sat, 5 Apr 2008 19:21:59 +0300
From:	"Alon Bar-Lev" <alon.barlev@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: SH4 - Cannot make initramfs work

Hello,

Can anyone help with this issue?
Maybe some idea of how to debug this further?

Thanks!

On 4/2/08, Alon Bar-Lev <alon.barlev@...il.com> wrote:
> Hello,
>
>  I am trying to boot 2.6.24 kernel on SH4 eb using embedded initramfs.
>
>  The kernel boots, but when trying to decompress the initramfs image it
>  fails with "crc error",
>  resulting from lib/inflate.c::gunzip:1250.
>
>  Has anyone got this error? The initramfs image is correct. I also
>  dumped the memory of __initramfs_start->__initramfs_start and verified
>  that it matches the initramfs image on usr/initramfs_data.cpio.gz.
>
>  I then noticed that the kernel code at
>  init/initramfs::unpack_to_rootfs:459 supports handling
>  uncompressed archives. So I compiled a kernel with uncompressed archived.
>
>  I also hooked the init/initramfs::do_name:585 functions, and see that
>  "/init' is passed
>  to sys_open, and sys_open returns with -EOENT (-2).
>
>  How can it be? shouldn't rootfs always be available?
>
>  The same attempt on i586, mipsel is working as expected.
>
>  Any ideas?
>  1. Why decompression working for kernel and not for initramfs (crc error).
>  2. Why files cannot be created on rootfs?
>
>  Thank you,
>
> Alon Bar-Lev.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/