From: Miao Xie <miaox@cn.fujitsu.com>
To: "Yan, Zheng" <zheng.yan@oracle.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 7/7] btrfs: fix a wrong error check in add_ra_bio_pages()
Date: Thu, 29 Jul 2010 18:47:16 +0800 [thread overview]
Message-ID: <4C515C34.9090005@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTim+U2s5-vHhmPqam9wj0+0_=01bq3JjnR=xB8T2@mail.gmail.com>
On Thu, 29 Jul 2010 18:38:39 +0800, Yan, Zheng wrote:
> 2010/7/29 Miao Xie<miaox@cn.fujitsu.com>:
>> From: Liu Bo<liubo2009@cn.fujitsu.com>
>>
>> Only when a page is not found by page_index, we'll go to the error check.
>>
>> Signed-off-by: Liu Bo<liubo2009@cn.fujitsu.com>
>> Signed-off-by: Miao Xie<miaox@cn.fujitsu.com>
>> ---
>> fs/btrfs/compression.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/btrfs/compression.c b/fs/btrfs/compression.c
>> index cb3877c..8458840 100644
>> --- a/fs/btrfs/compression.c
>> +++ b/fs/btrfs/compression.c
>> @@ -467,7 +467,7 @@ static noinline int add_ra_bio_pages(struct inode *inode,
>> rcu_read_lock();
>> page = radix_tree_lookup(&mapping->page_tree, page_index);
>> rcu_read_unlock();
>> - if (page) {
>> + if (!page) {
>> check_misses:
>> misses++;
>> if (misses> 4)
>
> This patch is wrong. The word "miss" here means "miss for read-ahead because
> the page is already in the page cache"
Oh, my mistake. Sorry!
Please ignore this patch.
Thanks for your review! How about the others?
Miao
>
> Yan, Zheng
>
>
prev parent reply other threads:[~2010-07-29 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 8:32 [PATCH 7/7] btrfs: fix a wrong error check in add_ra_bio_pages() Miao Xie
2010-07-29 10:38 ` Yan, Zheng
2010-07-29 10:47 ` Miao Xie [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=4C515C34.9090005@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zheng.yan@oracle.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 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).