From: Chris Mason <clm@fb.com>
To: David Sterba <dsterba@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL] Btrfs fixes for 4.12
Date: Fri, 9 Jun 2017 15:50:30 -0400 [thread overview]
Message-ID: <d4620eb4-1a53-12c8-f43c-1d8c13acd100@fb.com> (raw)
In-Reply-To: <cover.1496682964.git.dsterba@suse.com>
On 06/05/2017 01:47 PM, David Sterba wrote:
> Hi,
>
> please pull the following assorted fixes to 4.12. Thanks.
>
>
> The following changes since commit 9bcaaea7418d09691f1ffab5c49aacafe3eef9d0:
>
> btrfs: fix the gfp_mask for the reada_zones radix tree (2017-05-04 16:56:11 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris-4.12
>
> for you to fetch changes up to 2eec59665d545ce443184b9c7a32a65b4dde6d4c:
>
> Btrfs: clear EXTENT_DEFRAG bits in finish_ordered_io (2017-06-01 17:00:11 +0200)
>
> ----------------------------------------------------------------
> Colin Ian King (1):
> btrfs: fix incorrect error return ret being passed to mapping_set_error
>
> David Sterba (1):
> btrfs: use correct types for page indices in btrfs_page_exists_in_range
>
> Jan Kara (1):
> btrfs: Make flush bios explicitely sync
>
> Jeff Mahoney (2):
> btrfs: fix memory leak in update_space_info failure path
> btrfs: fix race with relocation recovery and fs_root setup
>
> Liu Bo (2):
> Btrfs: skip commit transaction if we don't have enough pinned bytes
Thanks Dave, I've been bashing on these along with Omar's enospc fix for
the last few days.
Omar mentioned that until we fix the pinned bytes counter we should
leave out this commit from Liu Bo, so I've rebased it out for now.
-chris
prev parent reply other threads:[~2017-06-09 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 17:47 [PULL] Btrfs fixes for 4.12 David Sterba
2017-06-09 19:50 ` Chris Mason [this message]
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=d4620eb4-1a53-12c8-f43c-1d8c13acd100@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.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 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).