cramfs as initrd still fails in 2.4.27-pre2 [PATCH]

cramfs as initrd still fails in 2.4.27-pre2 [PATCH]

[Santiago Garcia Mantinan]

Hi!

I've been trying to use the cramfs to hold my initrd images and it works ok
in 2.6.6, but when testing it in 2.4.26 or 2.4.27rc2 I get this problem:

RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 2128 blocks [1 disk] into ram disk... done.
Freeing initrd memory: 2128k freed
cramfs: wrong magic

In Debian official kernel packages cramfs is being used as the initrd, so I
had a look at Debian's kernel patches and extracted this one that makes
initrd work for me in 2.4.26 and 2.4.27-pre2:

diff -urN kernel-source-2.4.26/fs/block_dev.c kernel-source-2.4.26-1/fs/block_dev.c
--- kernel-source-2.4.26/fs/block_dev.c	2003-06-14 00:51:37.000000000 +1000
+++ kernel-source-2.4.26-1/fs/block_dev.c	2003-06-01 20:43:53.000000000 +1000
@@ -95,7 +95,7 @@
 	sync_buffers(dev, 2);
 	blksize_size[MAJOR(dev)][MINOR(dev)] = size;
 	bdev->bd_inode->i_blkbits = blksize_bits(size);
-	kill_bdev(bdev);
+	invalidate_bdev(bdev, 1);
 	bdput(bdev);
 	return 0;
 }

I think this patch or some other fix should be applied.

Regards...
-- 
Manty/BestiaTester -> http://manty.net

Re: cramfs as initrd still fails in 2.4.27-pre2 [PATCH]

[viro]

On Fri, May 14, 2004 at 03:29:55PM +0200, Santiago Garcia Mantinan wrote:
> In Debian official kernel packages cramfs is being used as the initrd, so I
> had a look at Debian's kernel patches and extracted this one that makes
> initrd work for me in 2.4.26 and 2.4.27-pre2:

Patch in debian kernel package is a mindless crap.  cramfs has no business
messing with block size (or buffer cache in general, to start with).  2.6
has it fixed the right way, there's a backport to 2.4 and IIRC it was
scheduled for inclusion.

Re: cramfs as initrd still fails in 2.4.27-pre2 [PATCH]

[Jeremy Jackson]

Santiago Garcia Mantinan wrote:
> Hi!
> 
> I've been trying to use the cramfs to hold my initrd images and it works ok
> in 2.6.6, but when testing it in 2.4.26 or 2.4.27rc2 I get this problem:
> 
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: Loading 2128 blocks [1 disk] into ram disk... done.
> Freeing initrd memory: 2128k freed
> cramfs: wrong magic

I just put ramdisk_blocksize=4096 on my kernel command line for 
kernel.org linux (debian's linux seems to work as is).

It would be nice if 2.4 didn't need that though.

-- 
Jeremy Jackson
Coplanar Networks
(519)897-1516
http://www.coplanar.net