From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] Btrfs: tree mod log fixes for 3.5-rc3
Date: Thu, 14 Jun 2012 19:16:32 +0200 [thread overview]
Message-ID: <1339694198-13388-1-git-send-email-list.btrfs@jan-o-sch.net> (raw)
Hi Chris,
This are my current fixes for the tree mod log. With these patches,
backref walking looks really stable now. My qgroup tests are getting
really close to succeeding :-)
Everything's pretty small and non-invasive, so it should be fine for the
upcomming rc.
You can also pull from
git://git.jan-o-sch.net/btrfs-unstable for-chris
Thanks,
Jan
Jan Schmidt (6):
Btrfs: remove call to btrfs_header_nritems with no effect
Btrfs: remove obsolete btrfs_next_leaf call from
__resolve_indirect_ref
Btrfs: use btrfs_read_lock_root_node in get_old_root
Btrfs: fix return value for __tree_mod_log_oldest_root
Btrfs: add btrfs_next_old_leaf
Btrfs: fix race in tree mod log addition
fs/btrfs/backref.c | 17 +++-------
fs/btrfs/ctree.c | 86 ++++++++++++++++++++++++++++++++++++++--------------
fs/btrfs/ctree.h | 2 +
3 files changed, 70 insertions(+), 35 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-06-14 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 17:16 Jan Schmidt [this message]
2012-06-14 17:16 ` [PATCH 1/6] Btrfs: remove call to btrfs_header_nritems with no effect Jan Schmidt
2012-06-14 17:16 ` [PATCH 2/6] Btrfs: remove obsolete btrfs_next_leaf call from __resolve_indirect_ref Jan Schmidt
2012-06-14 17:16 ` [PATCH 3/6] Btrfs: use btrfs_read_lock_root_node in get_old_root Jan Schmidt
2012-06-14 17:16 ` [PATCH 4/6] Btrfs: fix return value for __tree_mod_log_oldest_root Jan Schmidt
2012-06-14 17:16 ` [PATCH 5/6] Btrfs: add btrfs_next_old_leaf Jan Schmidt
2012-06-14 17:16 ` [PATCH 6/6] Btrfs: fix race in tree mod log addition 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=1339694198-13388-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).