| 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
| ||
|
Message-ID: <6934efce0705241322j7ad7c4fex621217e0749ddf3e@mail.gmail.com> Date: Thu, 24 May 2007 13:22:37 -0700 From: "Jared Hulbert" <jaredeh@...il.com> To: richard.griffiths@...driver.com Cc: Linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP On 5/22/07, Richard Griffiths <res07ml0@...izon.net> wrote: > Venerable cramfs fs Linear XIP patch originally from MontaVista, used in > the embedded Linux community for years, updated for 2.6.21. Tested on > several systems with NOR Flash. PXA270, TI OMAP2430, ARM Versatile and > Freescale iMX31ADS. > When trying to verify this patch on our PXA270 system we get the following error when running an XIP rootfs: cramfs: checking physical address 0xa00000 for linear cramfs image cramfs: linear cramfs image appears to be 3236 KB in size VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 96K /sbin/init: error while loading shared libraries: libgcc_s.so.1: failed to map segment from shared object: Error 11 Kernel panic - not syncing: Attempted to kill init! However, if our busybox binary is XIP while the libgcc_s.so.1 is not XIP, busybox runs fine. Richard, May I email you the rootfs tarball so you can recreate what we are seeing? It is a little less than 2MiB. The filing system executables will only run on a PXA27x processor. - 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/
Powered by blists - more mailing lists