From: Allison Henderson <achender@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: Allison Henderson <achender@linux.vnet.ibm.com>,
Yongqiang Yang <xiaoqiangnk@gmail.com>
Subject: [PATCH 3/6] ext4: initialize status extent tree
Date: Wed, 18 Apr 2012 00:07:15 -0700 [thread overview]
Message-ID: <1334732838-25102-4-git-send-email-achender@linux.vnet.ibm.com> (raw)
In-Reply-To: <1334732838-25102-1-git-send-email-achender@linux.vnet.ibm.com>
Let ext4 initialize status extent tree of a inode.
Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>
Signed-off-by: Allison Henderson <achender@linux.vnet.ibm.com>
---
:100644 100644 db2cd3f... da223a1... M fs/ext4/super.c
fs/ext4/super.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index db2cd3f..da223a1 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -898,6 +898,7 @@ static struct inode *ext4_alloc_inode(struct super_block *sb)
memset(&ei->i_cached_extent, 0, sizeof(struct ext4_ext_cache));
INIT_LIST_HEAD(&ei->i_prealloc_list);
spin_lock_init(&ei->i_prealloc_lock);
+ ext4_se_init_tree(&ei->i_se_tree);
ei->i_reserved_data_blocks = 0;
ei->i_reserved_meta_blocks = 0;
ei->i_allocated_meta_blocks = 0;
--
1.7.1
next prev parent reply other threads:[~2012-04-18 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 7:07 [PATCH 0/6] ext4: status extents Allison Henderson
2012-04-18 7:07 ` [PATCH 1/6] ext4: add two structures supporting status extent tree Allison Henderson
2012-04-18 7:07 ` [PATCH 2/6] ext4: add operations on " Allison Henderson
2012-04-18 7:07 ` Allison Henderson [this message]
2012-04-18 7:07 ` [PATCH 4/6] ext4: let ext4 maintian status extent trees Allison Henderson
2012-04-18 7:07 ` [PATCH 5/6] ext4: reimplement fiemap on status extent tree Allison Henderson
2012-04-18 7:07 ` [PATCH 6/6] ext4: reimplement ext4_find_delay_alloc_range " Allison Henderson
2012-04-19 1:56 ` [PATCH 0/6] ext4: status extents Darrick J. Wong
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=1334732838-25102-4-git-send-email-achender@linux.vnet.ibm.com \
--to=achender@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xiaoqiangnk@gmail.com \
/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).