From: Jens Axboe <axboe@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH/RFC: fix 2.5.20 ramdisk
Date: Tue, 4 Jun 2002 10:35:25 +0200 [thread overview]
Message-ID: <20020604083525.GA2512@suse.de> (raw)
In-Reply-To: <20020603180627.A23056@flint.arm.linux.org.uk>
On Mon, Jun 03 2002, Russell King wrote:
> 2.5.20 seems to be incapable of executing binaries in a ramdisk-based
> root filesystem. The ramdisk in question is an ext2fs, with a 1K
> block size loaded via the compressed ramdisk loader in do_mounts().
>
> It appears that, in the case of a 1K block sized filesystem, we attempt
> to read two 512-byte sectors into a BIO vector. The first one is copied
> into the first 512 bytes. The second sector, however, is copied over
> the first 512 bytes. Obviously not what we really want.
>
> Here is _a_ patch which solves this for me, which may not be correct.
> Jens?
Looks good.
--
Jens Axboe
next prev parent reply other threads:[~2002-06-04 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 17:06 PATCH/RFC: fix 2.5.20 ramdisk Russell King
2002-06-04 8:35 ` Jens Axboe [this message]
2002-06-04 8:45 ` Russell King
2002-06-04 7:54 ` Martin Dalecki
2002-06-04 8:53 ` Jens Axboe
2002-06-04 8:54 ` Russell King
2002-06-04 8:08 ` Martin Dalecki
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=20020604083525.GA2512@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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