From: Alexander Block <ablock84@googlemail.com>
To: linux-btrfs@vger.kernel.org
Cc: chris.mason@fusionio.com, Alexander Block <ablock84@googlemail.com>
Subject: [PATCH 0/2] Fix bugs in backref resolving code
Date: Tue, 19 Jun 2012 15:42:24 +0200 [thread overview]
Message-ID: <1340113346-12987-1-git-send-email-ablock84@googlemail.com> (raw)
This bug popped up while working on btrfs send. This patchset contains
two patches. The first one introduces btrfs_next_old_leaf which is needed
in the second patch which is the actual fix.
Both patches should probably go into 3.5 as they fix wrongly resolved
backrefs and a crash.
Big thanks to Jan Schmidt for his help here.
Alexander Block (2):
Btrfs: introduce btrfs_next_old_item
Btrfs: don't assume to be on the correct extent in add_all_parents
fs/btrfs/backref.c | 94 +++++++++++++++++++++++++++++-----------------------
fs/btrfs/ctree.h | 9 +++--
2 files changed, 59 insertions(+), 44 deletions(-)
--
1.7.10
next reply other threads:[~2012-06-19 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 13:42 Alexander Block [this message]
2012-06-19 13:42 ` [PATCH 1/2] Btrfs: introduce btrfs_next_old_item Alexander Block
2012-06-19 13:42 ` [PATCH 2/2] Btrfs: don't assume to be on the correct extent in add_all_parents Alexander Block
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=1340113346-12987-1-git-send-email-ablock84@googlemail.com \
--to=ablock84@googlemail.com \
--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).