From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.0-rc2
Date: Sun, 13 Jan 2019 17:39:38 +0100 [thread overview]
Message-ID: <cover.1547396230.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch to get:
- 2 regression fixes in clone/dedupe ioctls, the generic check callback
needs to lock extents properly and wait for io to avoid problems with
writeback and relocation
- fix deadlock when using free space tree due to block group creation
- a recently added check refuses a valid fileystem with seeding device,
make that work again with a quickfix, proper solution needs more
intrusive changes
Thanks.
----------------------------------------------------------------
The following changes since commit 52042d8e82ff50d40e76a275ac0b97aa663328b0:
btrfs: Fix typos in comments and strings (2018-12-17 14:51:50 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.0-rc1-tag
for you to fetch changes up to 1b3922a8bc74231f9a767d1be6d9a061a4d4eeab:
btrfs: Use real device structure to verify dev extent (2019-01-10 17:13:00 +0100)
----------------------------------------------------------------
Filipe Manana (3):
Btrfs: fix race between cloning range ending at eof and writeback
Btrfs: fix race between reflink/dedupe and relocation
Btrfs: fix deadlock when using free space tree due to block group creation
Qu Wenruo (1):
btrfs: Use real device structure to verify dev extent
fs/btrfs/ctree.c | 16 +++++++++-------
fs/btrfs/ioctl.c | 49 +++++++++++++++++++++++++++++++++++++++++++------
fs/btrfs/volumes.c | 12 ++++++++++++
3 files changed, 64 insertions(+), 13 deletions(-)
next reply other threads:[~2019-01-13 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 16:39 David Sterba [this message]
2019-01-13 18:05 ` [GIT PULL] Btrfs fixes for 5.0-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.1547396230.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--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.