public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] fix up indlen reservations on extent split
Date: Tue, 14 Oct 2014 17:59:13 -0400	[thread overview]
Message-ID: <1413323955-19976-1-git-send-email-bfoster@redhat.com> (raw)

Hi all,

Here's a couple patches to fix up the indirect block reservation
problem when splitting delalloc extents, described in more detail in the
patch 2 commit log.

This runs through xfstests without any explosions and quiets down
generic/033 when used in combination with the zero range rework (current
for-next includes the writeback on zero range workaround that also
prevents generic/033 asserts).

Brian

v1:
- xfs_bunmapi() code into independent patch.
- Refactor fix into separate helper function.
rfc: http://oss.sgi.com/archives/xfs/2014-09/msg00337.html

Brian Foster (2):
  xfs: update icsb freeblocks counter after extent deletion
  xfs: borrow indirect blocks from freed extent when available

 fs/xfs/libxfs/xfs_bmap.c | 159 ++++++++++++++++++++++++++++++++++-------------
 1 file changed, 116 insertions(+), 43 deletions(-)

-- 
1.8.3.1

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2014-10-14 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 21:59 Brian Foster [this message]
2014-10-14 21:59 ` [PATCH 1/2] xfs: update icsb freeblocks counter after extent deletion Brian Foster
2014-10-14 21:59 ` [PATCH 2/2] xfs: borrow indirect blocks from freed extent when available Brian Foster
2014-10-29 16:38 ` [PATCH 0/2] fix up indlen reservations on extent split Brian Foster
2014-10-29 20:02   ` Dave Chinner

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=1413323955-19976-1-git-send-email-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --cc=xfs@oss.sgi.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