From: Mike Galbraith <mikeg@wen-online.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [patchlet] cramfs incompatible with initrd..
Date: Wed, 14 Feb 2001 15:01:00 +0100 (CET) [thread overview]
Message-ID: <Pine.Linu.4.10.10102141445001.2324-100000@mikeg.weiden.de> (raw)
(If the initrd is other than PAGE_CACHE_SIZE blocksize)
Hi,
I found that merely having cramfs configured into the kernel
precludes mounting a ramdisk root after cramfs_read_super() has
been called. The problem is that cramfs changes the blocksize
of the ramdisk to PAGE_CACHE_SIZE after we've loaded the initrd
at 1k blocksize.
The patchlet below effectively works around the problem. Question
being does it do it in an acceptable manner? Can refusing to change
blocksize of a device with a registered hard blocksize cause problems
elsewhere?
-Mike
--- linux-2.4.1.ac12/fs/buffer.c.org Wed Feb 14 14:01:54 2001
+++ linux-2.4.1.ac12/fs/buffer.c Wed Feb 14 14:19:13 2001
@@ -686,7 +686,7 @@
int i, nlist, slept;
struct buffer_head * bh, * bh_next;
- if (!blksize_size[MAJOR(dev)])
+ if (!blksize_size[MAJOR(dev)] || get_hardblocksize(dev))
return;
/* Size must be a power of two, and between 512 and PAGE_SIZE */
reply other threads:[~2001-02-14 14:01 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=Pine.Linu.4.10.10102141445001.2324-100000@mikeg.weiden.de \
--to=mikeg@wen-online.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).