From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] Qgroup fixes for dirty hack routines
Date: Tue, 5 Jul 2016 17:32:04 +0800 [thread overview]
Message-ID: <20160705093207.14983-1-quwenruo@cn.fujitsu.com> (raw)
This patchset introduce 2 fixes for data extent owner hacks.
One can be triggered by balance, another one can be trigged by log replay
after power loss.
Root cause are all similar: EXTENT_DATA owner is changed by dirty
hacks, from swapping tree blocks containing EXTENT_DATA to manually
update extent backref without using inc/dec_extent_ref.
The first patch introduces needed functions, then 2 fixes.
The reproducer are all merged into xfstests, btrfs/123 and btrfs/119.
The 2nd patch is sent to mail list weeks ago, only commit message and
comment is updated.
Qu Wenruo (3):
btrfs: qgroup: Refactor btrfs_qgroup_insert_dirty_extent()
btrfs: relocation: Fix leaking qgroups numbers on data extents
btrfs: qgroup: Fix qgroup incorrectness caused by log replay
fs/btrfs/delayed-ref.c | 5 +---
fs/btrfs/extent-tree.c | 36 ++++------------------
fs/btrfs/qgroup.c | 39 ++++++++++++++++++++----
fs/btrfs/qgroup.h | 44 +++++++++++++++++++++++++--
fs/btrfs/relocation.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/tree-log.c | 16 ++++++++++
6 files changed, 178 insertions(+), 43 deletions(-)
--
2.9.0
next reply other threads:[~2016-07-05 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 9:32 Qu Wenruo [this message]
2016-07-05 9:32 ` [PATCH 1/3] btrfs: qgroup: Refactor btrfs_qgroup_insert_dirty_extent() Qu Wenruo
2016-07-05 9:32 ` [PATCH v2 2/3] btrfs: relocation: Fix leaking qgroups numbers on data extents Qu Wenruo
2016-07-05 9:32 ` [PATCH 3/3] btrfs: qgroup: Fix qgroup incorrectness caused by log replay Qu Wenruo
2016-07-27 2:37 ` [PATCH 0/3] Qgroup fixes for dirty hack routines Qu Wenruo
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=20160705093207.14983-1-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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).