linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] Btrfs: fixes for 3.5-rc5
Date: Wed, 27 Jun 2012 19:24:52 +0200	[thread overview]
Message-ID: <1340817899-16343-1-git-send-email-list.btrfs@jan-o-sch.net> (raw)

Hi Chris,

I expect this to be my last fixup set for the 3.5 series. All seven
fixes are pretty small, five of them for the tree mod log (3-7), one
generic for backref walking (2) and one fixing a starvation issue when
waiting for more delayed refs (1).

You can pull my patches based on your current for-linus from

	git://git.jan-o-sch.net/btrfs-unstable for-chris

I've run through xfstests as usual. All my backref walking tests are
succeeding now.

Even the qgroups patch set looks pretty good on top of these. If things
go well, I'll publish that patch series as soon as the current rc is
out, so there'll be plenty of time before 3.6.

Thanks,
-Jan

Jan Schmidt (7):
  Btrfs: avoid waiting for delayed refs when we must not
  Btrfs: support root level changes in __resolve_indirect_ref
  Btrfs: fix tree mod log for root replacements at leaf level
  Btrfs: always put insert_ptr modifications into the tree mod log
  Btrfs: leave critical region in btrfs_find_all_roots as soon as
    possible
  Btrfs: fix tree mod log rewind of ADD operations
  Btrfs: resolve tree mod log locking issue in btrfs_next_leaf

 fs/btrfs/backref.c     |   15 +++++++----
 fs/btrfs/ctree.c       |   60 ++++++++++++++++++++++++++++--------------------
 fs/btrfs/extent-tree.c |   11 ++++----
 3 files changed, 50 insertions(+), 36 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2012-06-27 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 17:24 Jan Schmidt [this message]
2012-06-27 17:24 ` [PATCH 1/7] Btrfs: avoid waiting for delayed refs when we must not Jan Schmidt
2012-06-27 17:24 ` [PATCH 2/7] Btrfs: support root level changes in __resolve_indirect_ref Jan Schmidt
2012-06-27 17:24 ` [PATCH 3/7] Btrfs: fix tree mod log for root replacements at leaf level Jan Schmidt
2012-06-27 17:24 ` [PATCH 4/7] Btrfs: always put insert_ptr modifications into the tree mod log Jan Schmidt
2012-06-27 17:24 ` [PATCH 5/7] Btrfs: leave critical region in btrfs_find_all_roots as soon as possible Jan Schmidt
2012-06-27 17:24 ` [PATCH 6/7] Btrfs: fix tree mod log rewind of ADD operations Jan Schmidt
2012-06-27 17:24 ` [PATCH 7/7] Btrfs: resolve tree mod log locking issue in btrfs_next_leaf Jan Schmidt

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=1340817899-16343-1-git-send-email-list.btrfs@jan-o-sch.net \
    --to=list.btrfs@jan-o-sch.net \
    --cc=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).