All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Herva <vherva@vianova.fi>
To: Norbert Federa <nfedera@thinstuff.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: block2mtd: Overrun end of disk in cache readahead
Date: Wed, 5 Jul 2006 13:07:27 +0300	[thread overview]
Message-ID: <20060705100727.GC15078@vianova.fi> (raw)
In-Reply-To: <44AB6EFA.9000604@thinstuff.com>

On Wed, Jul 05, 2006 at 09:49:14AM +0200, you [Norbert Federa] wrote:
> Ville,
> Try changing the PAGE_READAHEAD define in
> /drivers/mtd/devices/block2mtd.c from 64 to 0:
> 
> -#define PAGE_READAHEAD 64
> +#define PAGE_READAHEAD 0

Thanks.

Looking at the source, it almost looks like the error message is just a
spurious warning, not a dangerous error. Doesn't this happen when the
underlying device does not end at 64k boundary? And the readahead code just
stops reading ahead after that warning?



-- v -- 

v@iki.fi

  reply	other threads:[~2006-07-05 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  7:26 block2mtd: Overrun end of disk in cache readahead Ville Herva
2006-07-05  7:49 ` Norbert Federa
2006-07-05 10:07   ` Ville Herva [this message]
2006-07-05 11:22     ` Jörn Engel
2006-07-06  8:28       ` Ville Herva

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=20060705100727.GC15078@vianova.fi \
    --to=vherva@vianova.fi \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nfedera@thinstuff.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.