From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: [PULL] Btrfs fixes for 4.10
Date: Thu, 5 Jan 2017 16:22:08 +0100 [thread overview]
Message-ID: <cover.1483629310.git.dsterba@suse.com> (raw)
Hi,
a collection of fixes (lockdep, delayed ref locking, dio). The
btrfs_uuid_tree_iterate return value fix has a visible impact so it's added to
the mix. Please pull.
The following changes since commit 2939e1a86f758b55cdba73e29397dd3d94df13bc:
btrfs: limit async_work allocation and worker func duration (2016-12-13 11:01:30 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris-4.10
for you to fetch changes up to 3dda13a8ad787f3d4c4f18c8c05f8eebc7ea135a:
Merge branch 'misc-4.10' into for-chris-4.10-20170104 (2017-01-04 11:42:16 +0100)
----------------------------------------------------------------
David Sterba (1):
Merge branch 'misc-4.10' into for-chris-4.10-20170104
Jeff Mahoney (2):
btrfs: fix error handling when run_delayed_extent_op fails
btrfs: fix locking when we put back a delayed ref that's too new
Liu Bo (3):
Btrfs: use down_read_nested to make lockdep silent
Btrfs: fix lockdep warning about log_mutex
Btrfs: adjust outstanding_extents counter properly when dio write is split
Pan Bian (1):
btrfs: return the actual error value from from btrfs_uuid_tree_iterate
fs/btrfs/extent-tree.c | 8 ++++++--
fs/btrfs/inode.c | 11 +++++++++--
fs/btrfs/tree-log.c | 13 ++++++++++---
fs/btrfs/uuid-tree.c | 4 +---
4 files changed, 26 insertions(+), 10 deletions(-)
next reply other threads:[~2017-01-05 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:22 David Sterba [this message]
2017-01-05 16:24 ` [PULL] Btrfs fixes for 4.10 Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2017-01-20 14:42 David Sterba
2017-01-21 4:47 ` Chris Mason
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.1483629310.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.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.