public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix for initrd breakage in 2.5.13+
Date: Wed, 15 May 2002 19:54:22 +0100	[thread overview]
Message-ID: <20020515195421.C28997@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200205151653.g4FGrV702962@localhost.localdomain>

On Wed, May 15, 2002 at 12:53:31PM -0400, James Bottomley wrote:
> initrd was completely broken by your change set 1.447.69.4 ([PATCH] (4/6) 
> blksize_size[] removal).  As part of this change, you completely divorced the 
> ramdisk from the setup parameter rd_blocksize, so it now has the default 512 
> byte block size and thus initrd fails to mount.

Al has a far nicer patch for this, which works for me.  Al?

 Date:	Mon, 6 May 2002 03:03:04 -0400 (EDT)
 From:	Alexander Viro <viro@math.psu.edu>
 To:	Linus Torvalds <torvalds@transmeta.com>
 cc:	linux-kernel@vger.kernel.org
 Subject: [PATCH] rd.c blocksize fix

(fallout from blksize_size[] removal)

rd.c depends on exact value of blocksize being set from the very
beginning.

--- drivers/block/rd.c	Fri May  3 03:26:05 2002
+++ /tmp/rd.c	Mon May  6 03:00:00 2002
@@ -376,6 +376,7 @@
 		rd_bdev[unit] = bdget(kdev_t_to_nr(inode->i_rdev));
 		rd_bdev[unit]->bd_openers++;
 		rd_bdev[unit]->bd_inode->i_mapping->a_ops = &ramdisk_aops;
+		rd_bdev[unit]->bd_block_size = rd_blocksize;
 	}
 
 	return 0;

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-05-15 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 16:53 [PATCH] fix for initrd breakage in 2.5.13+ James Bottomley
2002-05-15 18:54 ` Russell King [this message]
2002-05-15 19:35   ` James Bottomley

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=20020515195421.C28997@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox