From: Sage Weil <sage@newdream.net>
To: Milosz Tanski <milosz@adfin.com>, Li Wang <liwang@ubuntukylin.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
ceph-devel <ceph-devel@vger.kernel.org>,
"linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
Sage Weil <sage@inktank.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ceph: allocate non-zero page to fscache in readpage()
Date: Sun, 10 Nov 2013 05:52:30 +0800 [thread overview]
Message-ID: <08e1e1e7-0187-4ef5-8019-c99b9d7c90a7@email.android.com> (raw)
In-Reply-To: <CANP1eJHthD-Q_Xv=HPWQjsJTHvpP2fj-X_j7HgBXaz5YKQ2EAQ@mail.gmail.com>
Added to the testing branch.
Thanks!
Milosz Tanski <milosz@adfin.com> wrote:
>Li, that's a good good catch.
>
>
>On Fri, Nov 8, 2013 at 9:26 PM, Li Wang <liwang@ubuntukylin.com> wrote:
>> ceph_osdc_readpages() returns number of bytes read, currently,
>> the code only allocate full-zero page into fscache, this patch
>> fixes this.
>>
>> Signed-off-by: Li Wang <liwang@ubuntukylin.com>
>> ---
>> fs/ceph/addr.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
>> index 6df8bd4..1e561c0 100644
>> --- a/fs/ceph/addr.c
>> +++ b/fs/ceph/addr.c
>> @@ -216,7 +216,7 @@ static int readpage_nounlock(struct file *filp,
>struct page *page)
>> }
>> SetPageUptodate(page);
>>
>> - if (err == 0)
>> + if (err >= 0)
>> ceph_readpage_to_fscache(inode, page);
>>
>> out:
>> --
>> 1.7.9.5
>>
>
>
>
>--
>Milosz Tanski
>CTO
>10 East 53rd Street, 37th floor
>New York, NY 10022
>
>p: 646-253-9055
>e: milosz@adfin.com
>--
>To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-11-09 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 2:26 [PATCH] Ceph: allocate non-zero page to fscache in readpage() Li Wang
2013-11-09 15:19 ` Milosz Tanski
2013-11-09 21:52 ` Sage Weil [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=08e1e1e7-0187-4ef5-8019-c99b9d7c90a7@email.android.com \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwang@ubuntukylin.com \
--cc=milosz@adfin.com \
--cc=sage@inktank.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).