From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fixes
Date: Fri, 27 Jan 2012 11:34:16 -0500 [thread overview]
Message-ID: <20120127163416.GE991@shiny> (raw)
[ sorry resend without bad auto-complete for lkml ]
Hi Linus,
We've got a variety pack of fixes in the for-linus branch of the btrfs
repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
These are all smaller fixes caught from different testers, benchmarks
and the occasional compiler warning.
Josef Bacik (3) commits (+3/-2):
Btrfs: use cluster->window_start when allocating from a cluster bitmap (+1/-1)
Btrfs: advance window_start if we're using a bitmap (+1/-0)
Btrfs: make sure a bitmap has enough bytes (+1/-1)
Stefan Behrens (1) commits (+6/-5):
Btrfs: fix warning for 32-bit build of fs/btrfs/check-integrity.c
Jan Schmidt (1) commits (+2/-2):
Btrfs: fix uninit warning in backref.c
Liu Bo (1) commits (+1/-1):
Btrfs: do not defrag a file partially
Mitch Harder (1) commits (+2/-0):
Btrfs: Check for NULL page in extent_range_uptodate
Chris Mason (1) commits (+8/-2):
Btrfs: fix reservations in btrfs_page_mkwrite
David Sterba (1) commits (+7/-0):
btrfs: mask out gfp flags in releasepage
Jan Kara (1) commits (+4/-2):
btrfs: Fix busyloops in transaction waiting code
Miao Xie (1) commits (+27/-22):
Btrfs: fix enospc error caused by wrong checks of the chunk
Total: (11) commits (+60/-36)
fs/btrfs/backref.c | 4 +-
fs/btrfs/check-integrity.c | 11 +++++----
fs/btrfs/disk-io.c | 7 ++++++
fs/btrfs/extent-tree.c | 49 +++++++++++++++++++++++-------------------
fs/btrfs/extent_io.c | 2 +
fs/btrfs/free-space-cache.c | 5 ++-
fs/btrfs/inode.c | 10 +++++++-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/tree-log.c | 6 +++-
9 files changed, 60 insertions(+), 36 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fixes
Date: Fri, 27 Jan 2012 11:34:16 -0500 [thread overview]
Message-ID: <20120127163416.GE991@shiny> (raw)
[ sorry resend without bad auto-complete for lkml ]
Hi Linus,
We've got a variety pack of fixes in the for-linus branch of the btrfs
repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
These are all smaller fixes caught from different testers, benchmarks
and the occasional compiler warning.
Josef Bacik (3) commits (+3/-2):
Btrfs: use cluster->window_start when allocating from a cluster bitmap (+1/-1)
Btrfs: advance window_start if we're using a bitmap (+1/-0)
Btrfs: make sure a bitmap has enough bytes (+1/-1)
Stefan Behrens (1) commits (+6/-5):
Btrfs: fix warning for 32-bit build of fs/btrfs/check-integrity.c
Jan Schmidt (1) commits (+2/-2):
Btrfs: fix uninit warning in backref.c
Liu Bo (1) commits (+1/-1):
Btrfs: do not defrag a file partially
Mitch Harder (1) commits (+2/-0):
Btrfs: Check for NULL page in extent_range_uptodate
Chris Mason (1) commits (+8/-2):
Btrfs: fix reservations in btrfs_page_mkwrite
David Sterba (1) commits (+7/-0):
btrfs: mask out gfp flags in releasepage
Jan Kara (1) commits (+4/-2):
btrfs: Fix busyloops in transaction waiting code
Miao Xie (1) commits (+27/-22):
Btrfs: fix enospc error caused by wrong checks of the chunk
Total: (11) commits (+60/-36)
fs/btrfs/backref.c | 4 +-
fs/btrfs/check-integrity.c | 11 +++++----
fs/btrfs/disk-io.c | 7 ++++++
fs/btrfs/extent-tree.c | 49 +++++++++++++++++++++++-------------------
fs/btrfs/extent_io.c | 2 +
fs/btrfs/free-space-cache.c | 5 ++-
fs/btrfs/inode.c | 10 +++++++-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/tree-log.c | 6 +++-
9 files changed, 60 insertions(+), 36 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-01-27 16:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 16:34 Chris Mason [this message]
2012-01-27 16:34 ` [GIT PULL] Btrfs fixes Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 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-23 18:49 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: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=20120127163416.GE991@shiny \
--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.