mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Remco van Mook <remco@virtu.nl>
To: Meelis Roos <mroos@linux.ee>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 odd behaviour of ramdisk + cramfs
Date: Thu, 13 Nov 2003 18:13:45 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20031113180820.026e6ba0@services3.virtu.nl> (raw)
In-Reply-To: <E1AKKos-0000Ix-T4@rhn.tartu-labor>


Hello Meelis,

thank you ! This patch works for me.

Does it have any side effects or might I suggest that this one is merged 
into the mainstream kernel ?

Cheers,

Remco van Mook

At 18:59 13-11-2003 +0200, Meelis Roos wrote:
>RvM> Running it once causes the mount to fail with 'cramfs: wrong magic' -
>
>Debian kernel has a patch to help cramfs initrd's work. The symptoms
>wothout the patch are very similar. This is the patch, extracted from
>Debian kernel-source package:
>
>diff -urN linux-2.4.22.orig/fs/block_dev.c linux-2.4.22/fs/block_dev.c
>--- linux-2.4.22.orig/fs/block_dev.c     2003-06-01 13:06:32.000000000 +1000
>+++ linux-2.4.22/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;
>  }
>
>--
>Meelis Roos (mroos@linux.ee)
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2003-11-13 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 16:32 Remco van Mook
2003-11-13 16:45 ` buffer/page cache aliasing? " bert hubert
2003-11-13 16:58   ` Remco van Mook
2003-11-13 16:59 ` Meelis Roos
2003-11-13 17:13   ` Remco van Mook [this message]
2003-11-13 17:41     ` Meelis Roos

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=5.1.0.14.2.20031113180820.026e6ba0@services3.virtu.nl \
    --to=remco@virtu.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®