From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com, Filipe Manana <fdmanana@suse.com>
Subject: [GIT PULL] Btrfs corruption fix and a couple cleanups
Date: Sat, 19 Nov 2016 13:44:10 +0000 [thread overview]
Message-ID: <1479563050-18185-1-git-send-email-fdmanana@kernel.org> (raw)
From: Filipe Manana <fdmanana@suse.com>
Hi Chris,
Here follows two cleanups and a fix for an issue that leads to a logical
corruption in the extent tree, where we end up with file extent items in
subvolume trees that don't have a matching extent item and back reference
in the extent tree after a balance when qgroups are enabled. This is a
regression introduced in 4.7 by a fix for yet another regression caused
by the last qgroups rework. This has been hitting SLE and openSUSE users
and QA very badly, where transactions keep getting aborted when running
delayed references leaving the root filesystem in RO mode and nearly
unusable. If you think it's appropriate, please consider it for
the 4.9 kernel (I've also tagged it for stable).
And of course, the two cleanups can wait for the 4.10 merge window.
Thanks.
The following changes since commit e3597e6090ddf40904dce6d0a5a404e2c490cac6:
Merge branch 'for-4.9-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.9 (2016-11-01 12:54:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux.git for-chris-4.10
for you to fetch changes up to 2a2a83de548f7afe2c27e51cbc9ff761cba2b61b:
Btrfs: remove rb_node field from the delayed ref node structure (2016-11-19 13:39:18 +0000)
----------------------------------------------------------------
Filipe Manana (3):
Btrfs: fix relocation incorrectly dropping data references
Btrfs: remove unused code when creating and merging reloc trees
Btrfs: remove rb_node field from the delayed ref node structure
fs/btrfs/delayed-ref.h | 6 ------
fs/btrfs/relocation.c | 34 ++++++++++++----------------------
2 files changed, 12 insertions(+), 28 deletions(-)
--
2.7.0.rc3
reply other threads:[~2016-11-23 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1479563050-18185-1-git-send-email-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--cc=clm@fb.com \
--cc=fdmanana@suse.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).