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.0-rc3
Date: Sun, 20 Jan 2019 16:51:29 +0100 [thread overview]
Message-ID: <cover.1547998923.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch to obtain a handful of fixes (some of
them in testing for a long time, were briefly mentioned in the 1st
pull):
- fix some test failures regarding cleanup after transaction abort
- revert of a patch that could cause a deadlock
- delayed iput fixes, that can help in ENOSPC situation when there's low
space and lot data to write
Thanks.
----------------------------------------------------------------
The following changes since commit 1b3922a8bc74231f9a767d1be6d9a061a4d4eeab:
btrfs: Use real device structure to verify dev extent (2019-01-10 17:13:00 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.0-rc2-tag
for you to fetch changes up to fd340d0f68cc87badfc9efcb226f23a5428826a0:
btrfs: wakeup cleaner thread when adding delayed iput (2019-01-18 17:27:23 +0100)
----------------------------------------------------------------
David Sterba (1):
Revert "btrfs: balance dirty metadata pages in btrfs_finish_ordered_io"
Josef Bacik (4):
btrfs: handle delayed ref head accounting cleanup in abort
btrfs: wait on ordered extents on abort cleanup
btrfs: run delayed iputs before committing
btrfs: wakeup cleaner thread when adding delayed iput
fs/btrfs/ctree.h | 7 +++++++
fs/btrfs/disk-io.c | 12 ++++++++++++
fs/btrfs/extent-tree.c | 21 ++++++++++++++-------
fs/btrfs/inode.c | 5 ++---
4 files changed, 35 insertions(+), 10 deletions(-)
next reply other threads:[~2019-01-20 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 15:51 David Sterba [this message]
2019-01-20 18:40 ` [GIT PULL] Btrfs fixes for 5.0-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.1547998923.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.