Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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.8-rc
Date: Thu,  8 Sep 2016 18:57:04 +0200	[thread overview]
Message-ID: <cover.1473353605.git.dsterba@suse.com> (raw)

Hi,

here are two fixups for the new space handling code introduced in 4.8.
Please pull.

----------------------------------------------------------------
The following changes since commit cb887083d084d74421ae7bb18acca40568da791f:

  Merge tag 'for-chris' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.8 (2016-09-01 17:29:34 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris

for you to fetch changes up to ce129655c9d9aaa7b3bcc46529db1b36693575ed:

  btrfs: introduce tickets_id to determine whether asynchronous metadata reclaim work makes progress (2016-09-06 16:31:43 +0200)

----------------------------------------------------------------
Wang Xiaoguang (2):
      btrfs: do not decrease bytes_may_use when replaying extents
      btrfs: introduce tickets_id to determine whether asynchronous metadata reclaim work makes progress

 fs/btrfs/ctree.h       |  1 +
 fs/btrfs/extent-tree.c | 23 +++++++++++++++--------
 2 files changed, 16 insertions(+), 8 deletions(-)

             reply	other threads:[~2016-09-08 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 16:57 David Sterba [this message]
2016-09-08 17:02 ` [PULL] Btrfs fixes for 4.8-rc 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.1473353605.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox