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-rc3
Date: Thu, 30 May 2019 12:44:01 +0200 [thread overview]
Message-ID: <cover.1559167316.git.dsterba@suse.com> (raw)
Hi,
a few more fixes for bugs reported by users, fuzzing tools and
regressions:
* fix crashes in relocation
* resuming interrupted balance operation does not properly clean up
orphan trees
* with enabled qgroups, resuming needs to be more careful about
block groups due to limited context when updating qgroups
* fsync and logging fixes found by fuzzing
* incremental send fixes for no-holes and clone
* fix spin lock type used in timer function for zstd
No merge conflicts, please pull. Thanks.
----------------------------------------------------------------
The following changes since commit 4e9845eff5a8027b5181d5bff56a02991fe46d48:
Btrfs: tree-checker: detect file extent items with overlapping ranges (2019-05-16 14:33:51 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.2-rc2-tag
for you to fetch changes up to 06989c799f04810f6876900d4760c0edda369cf7:
Btrfs: fix race updating log root item during fsync (2019-05-28 19:26:46 +0200)
----------------------------------------------------------------
Dennis Zhou (1):
btrfs: correct zstd workspace manager lock to use spin_lock_bh()
Filipe Manana (5):
Btrfs: incremental send, fix file corruption when no-holes feature is enabled
Btrfs: incremental send, fix emission of invalid clone operations
Btrfs: fix fsync not persisting changed attributes of a directory
Btrfs: fix wrong ctime and mtime of a directory after log replay
Btrfs: fix race updating log root item during fsync
Nikolay Borisov (1):
btrfs: Ensure replaced device doesn't have pending chunk allocation
Qu Wenruo (2):
btrfs: reloc: Also queue orphan reloc tree for cleanup to avoid BUG_ON()
btrfs: qgroup: Check bg while resuming relocation to avoid NULL pointer dereference
fs/btrfs/dev-replace.c | 35 +++++++++++++++++++++++----------
fs/btrfs/inode.c | 14 ++++++++++++--
fs/btrfs/qgroup.c | 8 +++++++-
fs/btrfs/relocation.c | 27 ++++++++++++++++++--------
fs/btrfs/send.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++---
fs/btrfs/tree-log.c | 20 ++++++-------------
fs/btrfs/zstd.c | 20 +++++++++----------
7 files changed, 128 insertions(+), 48 deletions(-)
next reply other threads:[~2019-05-30 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 10:44 David Sterba [this message]
2019-05-31 4:00 ` [GIT PULL] Btrfs fixes for 5.2-rc3 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.1559167316.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).