From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
clm@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.3-rc2
Date: Mon, 22 Jul 2019 14:18:08 +0200 [thread overview]
Message-ID: <cover.1563797135.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch with fixes for leaks caused by recently
merged patches, one build fix and a fix to prevent mixing of
incompatible features. Thanks.
----------------------------------------------------------------
The following changes since commit e02d48eaaed77f6c36916a7aa65c451e1f9d9aab:
btrfs: fix memory leak of path on error return path (2019-07-05 18:47:57 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.3-rc1-tag
for you to fetch changes up to 373c3b80e459cb57c34381b928588a3794eb5bbd:
btrfs: don't leak extent_map in btrfs_get_io_geometry() (2019-07-17 17:03:36 +0200)
----------------------------------------------------------------
Johannes Thumshirn (2):
btrfs: free checksum hash on in close_ctree
btrfs: don't leak extent_map in btrfs_get_io_geometry()
Qu Wenruo (1):
btrfs: inode: Don't compress if NODATASUM or NODATACOW set
YueHaibing (1):
btrfs: Fix build error while LIBCRC32C is module
fs/btrfs/Kconfig | 1 +
fs/btrfs/disk-io.c | 1 +
fs/btrfs/inode.c | 24 +++++++++++++++++++++++-
fs/btrfs/volumes.c | 10 +++++++---
4 files changed, 32 insertions(+), 4 deletions(-)
next reply other threads:[~2019-07-22 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 12:18 David Sterba [this message]
2019-07-22 16:40 ` [GIT PULL] Btrfs fixes for 5.3-rc2 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-07-26 16:42 David Sterba
2019-07-26 18:25 ` 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.1563797135.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.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.