From: Yunlei He <heyunlei@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [dev-test][PATCH 1/2] f2fs: add a missing truncate_inode_pages_final
Date: Fri, 10 Mar 2017 17:50:46 +0800 [thread overview]
Message-ID: <20170310095047.14540-1-heyunlei@huawei.com> (raw)
This patch add a missing truncate_inode_pages_final
Signed-off-by: Yunlei He <heyunlei@huawei.com>
---
fs/f2fs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index cfb40d3..7ad2606 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -642,6 +642,8 @@ static int f2fs_drop_inode(struct inode *inode)
if (f2fs_is_atomic_file(inode))
drop_inmem_pages(inode);
+ truncate_inode_pages_final(&inode->i_data);
+
/* should remain fi->extent_tree for writepage */
f2fs_destroy_extent_node(inode);
--
2.10.1
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
next reply other threads:[~2017-03-10 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:50 Yunlei He [this message]
2017-03-10 9:50 ` [PATCH 2/2] f2fs: avoid move encrypted block in BG_GC if it has been in memory Yunlei He
2017-03-13 18:30 ` Jaegeuk Kim
2017-03-14 1:37 ` heyunlei
2017-03-14 3:42 ` Chao Yu
2017-03-17 1:49 ` [dev-test][PATCH 1/2] f2fs: add a missing truncate_inode_pages_final Jaegeuk Kim
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=20170310095047.14540-1-heyunlei@huawei.com \
--to=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).