public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Milosz Tanski <milosz@adfin.com>
To: linux-cachefs@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Howells <dhowells@redhat.com>, NeilBrown <neilb@suse.de>
Subject: [PATCH 0/3] FS-Cache: Bug fixes for bugs that happen under vma pressure v2
Date: Wed, 13 Aug 2014 12:58:07 -0400	[thread overview]
Message-ID: <53EB991F.3070302@adfin.com> (raw)

FS-Cache has a few bugs generally only get tried in error mode / under
VMA preassure. The problem is exacerbated when majority of the IO is
cacheable netfs IO. At that point there are few pages that are evictable
due to GPF_NOFS allocation strategies.

The first bug is a recursive hang caused by fscache write out to ext4
which in turn needs to allocate pages and ends up calling releasepages()
on the netfs.

The second two bugs are cookie ref count bugs that happen when in the
error cases (mostly from related memory alloc failures).

This is the second try at this with Sign-Off lines, suggestions from
David and debug log on time out. With the log line we can further
investigate how often this happens and be smarter with the timeout (if
need be).

Milosz Tanski (3):
  FS-Cache: Timeout for releasepage()
  FS-Cache: Reduce cookie ref count if submit fails.
  FS-Cache: refcount becomes corrupt under vma pressure.

 fs/fscache/object.c |    2 ++
 fs/fscache/page.c   |   26 ++++++++++++++++++++++----
 2 files changed, 24 insertions(+), 4 deletions(-)

-- 
1.7.9.5


                 reply	other threads:[~2014-08-13 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53EB991F.3070302@adfin.com \
    --to=milosz@adfin.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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