LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pnasrat@redhat.com>
To: Doug Maxey <dwm@enoyolf.org>
Cc: Linux PowerPC List <linuxppc-dev@ozlabs.org>, yaboot-devel@ozlabs.org
Subject: Re: [PATCH 1/1] determine last ext3 LBA to fix wild LBA reads - v3
Date: Thu, 15 Feb 2007 12:25:26 +0000	[thread overview]
Message-ID: <1171542327.3387.70.camel@enki.eridu> (raw)
In-Reply-To: <1121.1167886652@bebe.enoyolf.org>

On Wed, 2007-01-03 at 22:57 -0600, Doug Maxey wrote:
> The issue seen in the current code is linux_read_blk() is
> (apparently) looking at the alternate offsets for all possible
> superblocks.  As yaboot scans each partition for all fs types, until
> it finds the appropriate signature, when searching the ext fs, libext2
> appears to calculate some blocks to read that may be 10x the size of
> the actual disk.

Thanks for this I've commited and it'll be in 1.3.14 shortly.

Sorry for the delay.

Paul

      reply	other threads:[~2007-02-15 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04  4:57 [PATCH 1/1] determine last ext3 LBA to fix wild LBA reads - v3 Doug Maxey
2007-02-15 12:25 ` Paul Nasrat [this message]

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=1171542327.3387.70.camel@enki.eridu \
    --to=pnasrat@redhat.com \
    --cc=dwm@enoyolf.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=yaboot-devel@ozlabs.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