From: Chris Mason <chris.mason@oracle.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Btrfs mailing list" <linux-btrfs@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs updates
Date: Mon, 27 Jun 2011 14:15:25 -0400 [thread overview]
Message-ID: <1309197689-sup-653@shiny> (raw)
Hi everyone,
The for-linus branch of the btrfs unstable tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git for-linus
Has our current set of fixes. Linus will probably notice the head
commit was from this morning. I reordered a refcount bump inside the
lock that protects the delayed inode tree and did a commit --amend.
This is just for clarity, the delayed_inode can't go away because it is
pinned by the inode itself. But, I don't want that code copy & pasted
elsewhere to create bugs later on.
These fix a regression in the new delayed_inode code where inodes that
are dropped from ram need to check for a delayed inode before we load
them back in.
Josef's commit avoids oopsen if the free extent cache had
to be discarded, and my commit makes sure a newly created empty file
gets logged properly if someone calls fsync on it.
Miao Xie (1) commits (+91/-26):
btrfs: fix inconsonant inode information
Josef Bacik (1) commits (+6/-3):
Btrfs: make sure to update total_bitmaps when freeing cache V3
Ilya Dryomov (1) commits (+2/-2):
Btrfs: fix type mismatch in find_free_extent()
Chris Mason (1) commits (+1/-0):
Btrfs: make sure to record the transid in new inodes
Total: (4) commits (+100/-31)
fs/btrfs/delayed-inode.c | 104 +++++++++++++++++++++++++++++++++----------
fs/btrfs/delayed-inode.h | 1 +
fs/btrfs/extent-tree.c | 4 +-
fs/btrfs/free-space-cache.c | 9 +++-
fs/btrfs/inode.c | 13 +++++-
5 files changed, 100 insertions(+), 31 deletions(-)
next reply other threads:[~2011-06-27 18:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 18:15 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 14:30 [GIT PULL] Btrfs updates Chris Mason
2013-03-29 17:47 Chris Mason
2013-03-09 0:38 Chris Mason
2013-02-16 1:55 Chris Mason
2012-12-17 21:44 Chris Mason
2012-08-29 16:01 Chris Mason
2012-07-05 19:55 Chris Mason
2012-06-21 15:47 Chris Mason
2012-06-15 18:09 Chris Mason
2012-06-15 23:57 ` Linus Torvalds
2012-06-16 0:21 ` Chris Mason
2012-06-01 13:18 Chris Mason
2012-04-13 13:38 Chris Mason
2012-03-10 2:01 Chris Mason
2012-02-24 16:41 Chris Mason
2011-12-01 15:39 Chris Mason
2011-08-18 18:04 Chris Mason
2011-07-27 22:46 Chris Mason
2011-06-20 1:12 Chris Mason
2011-06-12 11:57 Chris Mason
2011-06-12 18:08 ` Linus Torvalds
2011-06-13 1:02 ` Andi Kleen
2011-06-13 1:52 ` Chris Mason
2011-06-13 2:05 ` Li Zefan
2011-06-04 14:37 Chris Mason
2011-05-27 19:55 Chris Mason
2011-05-27 21:44 ` Chester
2011-05-15 14:47 Chris Mason
2011-04-26 14:24 Chris Mason
2011-04-18 14:26 Chris Mason
2011-02-15 3:49 Chris Mason
2011-02-07 20:12 Chris Mason
2011-01-17 21:13 Chris Mason
2010-12-14 1:54 Chris Mason
2010-05-27 15:15 Chris Mason
2010-05-27 17:18 ` Linus Torvalds
2010-05-27 17:32 ` Chris Mason
2010-05-27 17:47 ` Linus Torvalds
2010-06-02 2:59 ` Miao Xie
2010-09-12 12:38 ` Felipe Contreras
2010-04-05 19:36 Chris Mason
2010-04-06 15:40 ` Chris Mason
2010-03-15 19:18 Chris Mason
2010-03-16 21:01 ` Chris Mason
2010-03-18 16:59 ` Chris Mason
2009-10-15 0:06 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=1309197689-sup-653@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 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).