From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] Btrfs fixes
Date: Mon, 12 Apr 2010 16:00:54 -0400 [thread overview]
Message-ID: <20100412200054.GS13327@think> (raw)
Hi Linus
The last pull was missing two fixes, which you can find in the
master branch of the btrfs-unstable repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
Josef's commit helps close another enospc problem, and the other one
fixes an oops where we try to allocate a zero sized extent off the
drive.
Chris Mason (1) commits (+6/-0):
Btrfs: make sure the chunk allocator doesn't create zero length chunks
Josef Bacik (1) commits (+15/-5):
Btrfs: fix data enospc check overflow
Total: (2) commits
fs/btrfs/extent-tree.c | 20 +++++++++++++++-----
fs/btrfs/volumes.c | 6 ++++++
2 files changed, 21 insertions(+), 5 deletions(-)
next reply other threads:[~2010-04-12 20:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 20:00 Chris Mason [this message]
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2011-09-19 23:57 [GIT PULL] Btrfs fixes Chris Mason
2011-09-20 16:19 ` Sage Weil
2011-11-11 21:40 Chris Mason
2011-11-22 1:30 Chris Mason
2011-12-08 19:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-23 17:24 Chris Mason
2012-01-27 16:34 Chris Mason
2012-04-28 12:27 Chris Mason
2012-05-06 13:35 Chris Mason
2012-10-26 14:19 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
2013-02-07 0:13 Chris Mason
2013-03-17 12:34 Chris Mason
2014-09-19 19:47 Chris Mason
2014-11-01 16:05 Chris Mason
2015-01-08 18:28 Chris Mason
2015-01-23 18:49 Chris Mason
2015-03-20 16:55 Chris Mason
2015-04-26 13:18 Chris Mason
2015-05-01 14:08 Chris Mason
2015-05-15 19:11 Chris Mason
2017-01-13 22:01 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=20100412200054.GS13327@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 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).