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.7-rc4
Date: Mon, 27 Apr 2020 15:45:28 +0200 [thread overview]
Message-ID: <cover.1587992189.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch with regression fixes and some stable
material. Thanks.
* regression fixes:
* transaction leak when deleting unused block group
* log cleanup after transaction abort
* fix block group leak when removing fails
* transaction leak if relocation recovery fails
* fix SPDX header
----------------------------------------------------------------
The following changes since commit aec7db3b13a07d515c15ada752a7287a44a79ea0:
btrfs: fix setting last_trans for reloc roots (2020-04-17 15:20:08 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.7-rc3-tag
for you to fetch changes up to 1402d17dfd9657be0da8458b2079d03c2d61c86a:
btrfs: fix transaction leak in btrfs_recover_relocation (2020-04-23 17:24:56 +0200)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: fix memory leak of transaction when deleting unused block group
Josef Bacik (1):
btrfs: drop logs when we've aborted a transaction
Nishad Kamdar (1):
btrfs: discard: Use the correct style for SPDX License Identifier
Xiyu Yang (2):
btrfs: fix block group leak when removing fails
btrfs: fix transaction leak in btrfs_recover_relocation
fs/btrfs/block-group.c | 20 ++++++++++++++------
fs/btrfs/discard.h | 2 +-
fs/btrfs/disk-io.c | 36 ++++++++++++++++++++++++++++++++----
fs/btrfs/relocation.c | 1 +
4 files changed, 48 insertions(+), 11 deletions(-)
next reply other threads:[~2020-04-27 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 13:45 David Sterba [this message]
2020-04-27 20:40 ` [GIT PULL] Btrfs fixes for 5.7-rc4 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.1587992189.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.