From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: linux-kernel@vger.kernel.org
Cc: Alexander Viro <viro@math.psu.edu>,
Torrey Hoffman <torrey.hoffman@myrio.com>,
<andersen@codepoet.org>
Subject: [BUG] cramfs+initrd: BOOM! (Re: ramdisk corruption problems)
Date: Thu, 20 Dec 2001 12:11:05 -0200 [thread overview]
Message-ID: <01122012110506.01835@manta> (raw)
[fifth (!) attempt, previous mails did not show up on lkml]
[This msg definitely does not want to make it into the list :-)]
At last I have found one definite bug (maybe there are others).
I was unable to load a minix initrd on any 2.4.12+ kernel. 2.4.10 is fine.
Thanks to Mike Galbraith <mikeg@wen-online.de> who said that he can load
minix initrds and sent me both .config and initrd. I found out that with his
.config I indeed can load my initrd. After many recompilations and reboots
(binary search :-) it turned out that compiled-in support for cramfs caused
initrds to be corrupted.
[update since 3rd attempt to reach lkml]
I did some debugging in fs/cramfs/inode.c:cramfs_read_super()
If I plant immediate "return 0;" there initrd loads.
If I place "return 0;" after "set_blocksize(sb->s_dev, PAGE_CACHE_SIZE);"
- BOOM! Kernel panic. Restoring blocksize to 1024 prior to return does NOT
help.
[end update]
This is the diff between 'good' and 'bad' .config:
--- .config.good Tue Dec 18 22:21:20 2001
+++ .config.bad Tue Dec 18 22:21:10 2001
@@ -716,7 +716,7 @@
CONFIG_EFS_FS=m
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
-# CONFIG_CRAMFS is not set
+CONFIG_CRAMFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
@@ -767,7 +767,7 @@
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set
-# CONFIG_ZLIB_FS_INFLATE is not set
+CONFIG_ZLIB_FS_INFLATE=y
#
# Partition Types
See?
Hope this info is useful.
--
vda
reply other threads:[~2001-12-20 10:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01122012110506.01835@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torrey.hoffman@myrio.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.