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.8-rc7
Date: Fri, 24 Jul 2020 13:21:32 +0200 [thread overview]
Message-ID: <cover.1595587350.git.dsterba@suse.com> (raw)
Hi,
I've selected a few resouce leak fixes from recent patches, all are
stable material. The problems have been observed during testing or have
a reproducer.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit d77765911385b65fc82d74ab71b8983cddfe0b58:
btrfs: wire up iter_file_splice_write (2020-07-09 19:57:58 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.8-rc6-tag
for you to fetch changes up to 48cfa61b58a1fee0bc49eef04f8ccf31493b7cdd:
btrfs: fix mount failure caused by race with umount (2020-07-21 22:08:54 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix mount failure caused by race with umount
Filipe Manana (1):
btrfs: fix double free on ulist after backref resolution failure
Qu Wenruo (1):
btrfs: qgroup: fix data leak caused by race between writeback and truncate
Robbie Ko (1):
btrfs: fix page leaks after failure to lock page for delalloc
fs/btrfs/backref.c | 1 +
fs/btrfs/extent_io.c | 3 ++-
fs/btrfs/inode.c | 23 ++++++++++-------------
fs/btrfs/volumes.c | 8 ++++++++
4 files changed, 21 insertions(+), 14 deletions(-)
next reply other threads:[~2020-07-24 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 11:21 David Sterba [this message]
2020-07-24 21:40 ` [GIT PULL] Btrfs fixes for 5.8-rc7 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.1595587350.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