From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong1@huawei.com>,
jaegeuk@kernel.org, yuchao0@huawei.com
Cc: miaoxie@huawei.com, heyunlei@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [RFC PATCH 1/5] mkfs.f2fs: introduce mkfs parameters in f2fs_configuration
Date: Thu, 8 Feb 2018 21:30:55 +0800 [thread overview]
Message-ID: <0cf30d18-1ccf-f09e-2f9a-79e2673cd00b@kernel.org> (raw)
In-Reply-To: <20180206043125.134191-2-shengyong1@huawei.com>
On 2018/2/6 12:31, Sheng Yong wrote:
> /* only root inode was written before truncating dnodes */
> last_inode_pos = start_inode_pos +
> - c.cur_seg[CURSEG_HOT_NODE] * c.blks_per_seg + quota_inum;
> + c.cur_seg[CURSEG_HOT_NODE] * c.blks_per_seg + c.quota_inum;
- f2fs_create_root_dir
- f2fs_write_root_inode
- discard_obsolete_dnode
access c.quota_inum
- f2fs_write_qf_inode
update c.quota_inum
Should c.quota_inum be initialized more early?
Thanks,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-02-08 13:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 4:31 [RFC PATCH 0/5] f2fs-tools: introduce lost+found feature Sheng Yong
2018-02-06 4:31 ` [RFC PATCH 1/5] mkfs.f2fs: introduce mkfs parameters in f2fs_configuration Sheng Yong
2018-02-08 13:30 ` Chao Yu [this message]
2018-02-09 3:21 ` Sheng Yong
2018-02-09 12:59 ` Chao Yu
2018-02-06 4:31 ` [RFC PATCH 2/5] f2fs-tools: init f2fs_configuration as 0 Sheng Yong
2018-02-08 13:32 ` Chao Yu
2018-02-10 2:49 ` Jaegeuk Kim
2018-02-06 4:31 ` [RFC PATCH 3/5] fsck.f2fs: integrate sanity_check_inode to __check_inode_mode Sheng Yong
2018-02-08 13:44 ` Chao Yu
2018-02-06 4:31 ` [RFC PATCH 4/5] mkfs.f2fs: create lost+found directory Sheng Yong
2018-02-08 15:08 ` Chao Yu
2018-02-09 3:21 ` Sheng Yong
2018-02-09 13:13 ` Chao Yu
2018-02-06 4:31 ` [RFC PATCH 5/5] fsck.f2fs: reconnect unreachable files to lost+found Sheng Yong
2018-02-07 10:01 ` Sheng Yong
2018-02-07 10:04 ` Sheng Yong
2018-02-13 14:22 ` Chao Yu
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=0cf30d18-1ccf-f09e-2f9a-79e2673cd00b@kernel.org \
--to=chao@kernel.org \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=miaoxie@huawei.com \
--cc=shengyong1@huawei.com \
--cc=yuchao0@huawei.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).