From: Chris Mason <chris.mason@oracle.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: Problem found, but why???
Date: Wed, 02 Feb 2011 16:51:01 -0500 [thread overview]
Message-ID: <1296683256-sup-5329@think> (raw)
In-Reply-To: <4D49A69C.4040801@panasas.com>
Excerpts from Boaz Harrosh's message of 2011-02-02 13:46:52 -0500:
> 115e19c53501edc11f730191f7f047736815ae3d is the first bad commit
> commit 115e19c53501edc11f730191f7f047736815ae3d
> Author: Boaz Harrosh <Boaz Harrosh bharrosh@panasas.com>
>
> exofs: Set i_mapping->backing_dev_info anyway
>
> OK It's stupid ME. But why please someone explain this issue?
> For now I'll send a revert, but I would like this explained,
> perhaps a more solid fix is needed.
The bdi_init code doesn't seem to set the ra_pages to a default number.
You got there via kzalloc, so the ra_pages field in your bdi is probably
zero.
This should stop all readahead.
-chris
next prev parent reply other threads:[~2011-02-02 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 16:48 Please Help: 2.6.37 a_ops->readpages is never called, 2.6.36 was fine Boaz Harrosh
2011-02-02 18:46 ` Problem found, but why??? Boaz Harrosh
2011-02-02 21:51 ` Chris Mason [this message]
2011-02-03 11:22 ` [PATCH] exofs: Fix read ahead BUG, caused by moving inodes to sb->s_bdi Boaz Harrosh
2011-02-03 12:12 ` Boaz Harrosh
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=1296683256-sup-5329@think \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=viro@zeniv.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;
as well as URLs for NNTP newsgroup(s).