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.2-rc2
Date: Mon, 20 May 2019 18:52:43 +0200 [thread overview]
Message-ID: <cover.1558370339.git.dsterba@suse.com> (raw)
Hi,
the branch contains fixes, notable hilights:
* fixes for some long-standing bugs in fsync that were quite hard to
catch but now finaly fixed
* some fixups to error handling paths that did not properly clean up
(locking, memory)
* fix to space reservation for inheriting properties
No merge conflicts, please pull. Thanks.
----------------------------------------------------------------
The following changes since commit b1c16ac978fd40ae636e629bb69a652df7eebdc2:
btrfs: Use kvmalloc for allocating compressed path context (2019-05-02 13:48:19 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.2-rc1-tag
for you to fetch changes up to 4e9845eff5a8027b5181d5bff56a02991fe46d48:
Btrfs: tree-checker: detect file extent items with overlapping ranges (2019-05-16 14:33:51 +0200)
----------------------------------------------------------------
Filipe Manana (4):
Btrfs: do not abort transaction at btrfs_update_root() after failure to COW path
Btrfs: avoid fallback to transaction commit during fsync of files with holes
Btrfs: fix race between ranged fsync and writeback of adjacent ranges
Btrfs: tree-checker: detect file extent items with overlapping ranges
Johnny Chang (1):
btrfs: Check the compression level before getting a workspace
Josef Bacik (2):
btrfs: don't double unlock on error in btrfs_punch_hole
btrfs: use the existing reserved items for our first prop for inheritance
Qu Wenruo (1):
btrfs: extent-tree: Fix a bug that btrfs is unable to add pinned bytes
Tobin C. Harding (2):
btrfs: sysfs: Fix error path kobject memory leak
btrfs: sysfs: don't leak memory when failing add fsid
fs/btrfs/compression.c | 1 +
fs/btrfs/extent-tree.c | 15 ++++++++-------
fs/btrfs/file.c | 16 +++++++++++++---
fs/btrfs/props.c | 30 ++++++++++++++++++++++--------
fs/btrfs/root-tree.c | 4 +---
fs/btrfs/sysfs.c | 7 ++++++-
fs/btrfs/tree-checker.c | 49 +++++++++++++++++++++++++++++++++++++++++++++----
fs/btrfs/tree-log.c | 1 +
8 files changed, 97 insertions(+), 26 deletions(-)
next reply other threads:[~2019-05-20 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 16:52 David Sterba [this message]
2019-05-20 17:00 ` [GIT PULL] Btrfs fixes for 5.2-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.1558370339.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.