All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: <torvalds@linux-foundation.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fixes
Date: Fri, 23 Jan 2015 13:49:18 -0500	[thread overview]
Message-ID: <20150123184911.GA17437@ret.masoncoding.com> (raw)

Hi Linus,

We have a few fixes in my for-linus branch:

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

Qu Wenruo's batch fix a regression between some our merge window pull
and the inode_cache feature.  The rest are smaller bugs.

Qu Wenruo (2) commits (+11/-1):
    btrfs: Don't call btrfs_start_transaction() on frozen fs to avoid deadlock. (+10/-0)
    btrfs: Fix the bug that fs_info->pending_changes is never cleared. (+1/-1)

Satoru Takeuchi (1) commits (+1/-1):
    btrfs: fix state->private cast on 32 bit machines

David Sterba (1) commits (+2/-2):
    btrfs: sync ioctl, handle errors after transaction start

Filipe Manana (1) commits (+2/-1):
    Btrfs: fix race deleting block group from space_info->ro_bgs list

Tsutomu Itoh (1) commits (+1/-1):
    Btrfs: fix incorrect freeing in scrub_stripe

Total: (6) commits (+17/-6)

 fs/btrfs/ctree.h       |  1 +
 fs/btrfs/extent-tree.c |  2 +-
 fs/btrfs/extent_io.c   |  2 +-
 fs/btrfs/scrub.c       |  2 +-
 fs/btrfs/super.c       | 14 ++++++++++++--
 fs/btrfs/transaction.c |  2 +-
 6 files changed, 17 insertions(+), 6 deletions(-)

             reply	other threads:[~2015-01-23 18:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 18:49 Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 [GIT PULL] Btrfs fixes Chris Mason
2015-11-05 11:20 fdmanana
2015-11-05 14:59 ` Chris Mason
2015-05-15 19:11 Chris Mason
2015-05-01 14:08 Chris Mason
2015-04-26 13:18 Chris Mason
2015-03-20 16:55 Chris Mason
2015-01-08 18:28 Chris Mason
2014-11-01 16:05 Chris Mason
2014-09-19 19:47 Chris Mason
2013-03-17 12:34 Chris Mason
2013-02-07  0:13 Chris Mason
2013-02-07  0:09 Chris Mason
2013-01-23  0:48 Chris Mason
2013-01-23  1:28 ` Liu Bo
2013-01-23  1:40   ` Chris Mason
2013-01-24 21:52 ` Chris Mason
2013-01-25  3:13   ` Linus Torvalds
2012-10-26 14:19 Chris Mason
2012-05-06 13:35 Chris Mason
2012-04-28 12:27 Chris Mason
2012-01-27 16:34 Chris Mason
2012-01-27 16:34 ` Chris Mason
2012-01-27 16:31 Chris Mason
2011-12-23 17:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-16 18:29 ` nobody
2011-12-08 19:24 Chris Mason
2011-11-22  1:30 Chris Mason
2011-11-11 21:40 Chris Mason
2011-09-19 23:57 Chris Mason
2011-09-20 16:19 ` Sage Weil
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2010-04-12 20:00 [GIT PULL] Btrfs fixes 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=20150123184911.GA17437@ret.masoncoding.com \
    --to=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.