From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.4-rc2
Date: Mon, 30 Sep 2019 16:25:08 +0200 [thread overview]
Message-ID: <cover.1569852875.git.dsterba@suse.com> (raw)
Hi,
a bunch of fixes that accumulated in recent weeks, mostly material for
stable.
Summary:
- fix for regression from 5.3 that prevents to use balance convert with
single profile
- qgroup fixes: rescan race, accounting leak with multiple writers,
potential leak after io failure recovery
- fix for use after free in relocation (reported by KASAN)
- other error handling fixups
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 6af112b11a4bc1b560f60a618ac9c1dcefe9836e:
btrfs: Relinquish CPUs in btrfs_compare_trees (2019-09-09 14:59:20 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.4-rc1-tag
for you to fetch changes up to d4e204948fe3e0dc8e1fbf3f8f3290c9c2823be3:
btrfs: qgroup: Fix reserved data space leak if we have multiple reserve calls (2019-09-27 15:24:34 +0200)
----------------------------------------------------------------
Dennis Zhou (1):
btrfs: adjust dirty_metadata_bytes after writeback failure of extent buffer
Filipe Manana (3):
Btrfs: fix selftests failure due to uninitialized i_mode in test inodes
Btrfs: fix missing error return if writeback for extent buffer never started
Btrfs: fix race setting up and completing qgroup rescan workers
Qu Wenruo (4):
btrfs: relocation: fix use-after-free on dead relocation roots
btrfs: Fix a regression which we can't convert to SINGLE profile
btrfs: qgroup: Fix the wrong target io_tree when freeing reserved data space
btrfs: qgroup: Fix reserved data space leak if we have multiple reserve calls
fs/btrfs/extent_io.c | 13 +++++++++++++
fs/btrfs/qgroup.c | 38 +++++++++++++++++++++++---------------
fs/btrfs/relocation.c | 9 ++++++++-
fs/btrfs/tests/btrfs-tests.c | 8 +++++++-
fs/btrfs/volumes.c | 8 +++++++-
5 files changed, 58 insertions(+), 18 deletions(-)
next reply other threads:[~2019-09-30 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 14:25 David Sterba [this message]
2019-09-30 17:30 ` [GIT PULL] Btrfs fixes for 5.4-rc2 pr-tracker-bot
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=cover.1569852875.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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