All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: <torvalds@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
	<linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] btrfs update
Date: Fri, 19 Jul 2013 15:17:40 -0400	[thread overview]
Message-ID: <20130719191740.GA2255@localhost.localdomain> (raw)

Hello,

I'm playing the role of Chris Mason this week while he's on vacation.  There are
a few critical fixes for btrfs here, all regressions and have been tested well.
Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git for-linus

I've based it off a recent pull of your tree, hopefully that's the right thing.
Thanks,

Josef Bacik (3):
      Btrfs: update drop progress before stopping snapshot dropping
      Btrfs: fix lock leak when resuming snapshot deletion
      Btrfs: re-add root to dead root list if we stop dropping it

Stefan Behrens (1):
      Btrfs: fix wrong write offset when replacing a device

 fs/btrfs/extent-tree.c |   27 +++++++++++++++++++++------
 fs/btrfs/scrub.c       |    2 +-
 2 files changed, 22 insertions(+), 7 deletions(-)

                 reply	other threads:[~2013-07-19 19:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130719191740.GA2255@localhost.localdomain \
    --to=jbacik@fusionio.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.