From: David Howells <dhowells@redhat.com>
To: Milosz Tanski <milosz@adfin.com>
Cc: linux-fsdevel@vger.kernel.org, NeilBrown <neilb@suse.de>,
linux-cachefs@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] FS-Cache: Timeout for releasepage()
Date: Wed, 27 Aug 2014 15:29:01 +0100 [thread overview]
Message-ID: <32460.1409149741@warthog.procyon.org.uk> (raw)
In-Reply-To: <53EB9928.1030601@adfin.com>
Milosz Tanski <milosz@adfin.com> wrote:
> + * since we might be called recusively via parent fs.
I've changed that to "recursively".
> +bool relase_page_wait_timeout(struct fscache_cookie *cookie, struct page *page)
I've changed that to "release_page_wait_timeout()".
> + if (!relase_page_wait_timeout(cookie, page)) {
> + _debug("fscache writeout timeout page: %p{%lx}",
> + page, page->index);
> + }
And I've dropped the braces there.
David
next prev parent reply other threads:[~2014-08-27 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1407948737.git.milosz@adfin.com>
2014-08-13 16:58 ` [PATCH 1/3] FS-Cache: Timeout for releasepage() Milosz Tanski
2014-08-13 16:58 ` [PATCH 2/3] FS-Cache: Reduce cookie ref count if submit fails Milosz Tanski
2014-08-14 4:23 ` NeilBrown
2014-08-13 16:58 ` [PATCH 3/3] FS-Cache: refcount becomes corrupt under vma pressure Milosz Tanski
2014-08-27 14:29 ` David Howells [this message]
2014-08-27 14:31 ` [PATCH 2/3] FS-Cache: Reduce cookie ref count if submit fails David Howells
2014-09-04 16:00 ` Milosz Tanski
2014-09-08 15:55 ` Milosz Tanski
2014-09-17 20:23 ` David Howells
2014-09-17 20:24 ` Milosz Tanski
[not found] <cover.1406043029.git.milosz@adfin.com>
2014-07-22 15:50 ` [PATCH 1/3] FS-Cache: Timeout for releasepage() Milosz Tanski
2014-07-29 15:32 ` David Howells
2014-07-29 15:35 ` Milosz Tanski
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=32460.1409149741@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=neilb@suse.de \
/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).