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 updates for 5.1, part 2
Date: Tue, 12 Mar 2019 16:08:52 +0100 [thread overview]
Message-ID: <cover.1552401006.git.dsterba@suse.com> (raw)
Hi,
here's the second part containing mostly fixes. The changelog would
repeat the subject lines, in summary there are correctness and a
deadlock fixes. Please pull, thanks.
----------------------------------------------------------------
The following changes since commit f65e25e343cfc0e6f4db9a687c4085fad268325d:
btrfs: Remove unnecessary casts in btrfs_read_root_item (2019-02-25 14:19:23 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.1-part2-tag
for you to fetch changes up to d3865159ac7823f645d313fdbac0b256ac01eeb9:
btrfs: zstd: ensure reclaim timer is properly cleaned up (2019-02-27 17:45:04 +0100)
----------------------------------------------------------------
David Sterba (1):
btrfs: move ulist allocation out of transaction in quota enable
Dennis Zhou (1):
btrfs: zstd: ensure reclaim timer is properly cleaned up
Filipe Manana (2):
Btrfs: fix corruption reading shared and compressed extents after hole punching
Btrfs: fix deadlock between clone/dedupe and rename
Josef Bacik (2):
btrfs: check for refs on snapshot delete resume
btrfs: save drop_progress if we drop refs at all
fs/btrfs/ctree.h | 2 ++
fs/btrfs/extent-tree.c | 74 +++++++++++++++++++++++++++++++++++++++++++++-----
fs/btrfs/extent_io.c | 4 +--
fs/btrfs/ioctl.c | 21 ++------------
fs/btrfs/qgroup.c | 13 ++++-----
fs/btrfs/root-tree.c | 8 ++++--
fs/btrfs/zstd.c | 6 ++--
7 files changed, 90 insertions(+), 38 deletions(-)
next reply other threads:[~2019-03-12 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:08 David Sterba [this message]
2019-03-12 22:20 ` [GIT PULL] Btrfs updates for 5.1, part 2 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.1552401006.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.