All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-btrfs@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.33
Date: Thu, 4 Feb 2010 20:59:14 -0500	[thread overview]
Message-ID: <20100205015913.GA2770@think> (raw)

Hello everyone,

The master branch of the btrfs unstable tree:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master

Has a small collection of fixes.  These are mostly bugs, but I put in
one of Josef's safer performance tweaks as well.

Aneesh Kumar K.V (1) commits (+3/-1):
    Btrfs: apply updated fallocate i_size fix

Josef Bacik (1) commits (+2/-44):
    Btrfs: do not try and lookup the file extent when finishing ordered io

Miao Xie (1) commits (+8/-2):
    Btrfs: remove BUG_ON() due to mounting bad filesystem

Roel Kluin (1) commits (+1/-1):
    Btrfs: make error return negative in btrfs_sync_file()

Zheng Yan (2) commits (+5/-6):
    Btrfs: fix race between allocate and release extent buffer. (+1/-2)
    Btrfs: Fix oopsen when dropping empty tree. (+4/-4)

Total: (6) commits

 fs/btrfs/disk-io.c     |    7 +++++-
 fs/btrfs/extent-tree.c |    8 +++----
 fs/btrfs/extent_io.c   |    3 --
 fs/btrfs/file.c        |    2 -
 fs/btrfs/inode.c       |   50 ++++---------------------------------------------
 fs/btrfs/relocation.c  |    3 +-
 6 files changed, 19 insertions(+), 54 deletions(-)

             reply	other threads:[~2010-02-05  1:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  1:59 Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-29 17:35 [GIT PULL] Btrfs updates for 2.6.33 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=20100205015913.GA2770@think \
    --to=chris.mason@oracle.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.