From: Yunlei He <heyunlei@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Cc: ning.jia@huawei.com, heyunlei@huawei.com
Subject: [PATCH] f2fs: avoid endless loop in funtion f2fs_sync_inode_meta
Date: Tue, 7 Nov 2017 10:23:58 +0800 [thread overview]
Message-ID: <1510021438-23206-1-git-send-email-heyunlei@huawei.com> (raw)
One inode may be evicted without removing from global dirty list,
which will cause endless loop in funtion f2fs_sync_inode_meta.
Signed-off-by: Yunlei He <heyunlei@huawei.com>
---
fs/f2fs/inode.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index 9684d535..ce1f87d 100644
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.c
@@ -532,6 +532,13 @@ void f2fs_evict_inode(struct inode *inode)
if (err)
update_inode_page(inode);
+
+ if (unlikely(is_inode_flag_set(inode, FI_DIRTY_INODE))) {
+ f2fs_inode_synced(inode);
+ f2fs_msg(sbi->sb, KERN_WARNING, "correct inode status to avoid "
+ "endless loop, since inode writeback flow is broken");
+ f2fs_bug_on(sbi, 1);
+ }
dquot_free_inode(inode);
sb_end_intwrite(inode->i_sb);
no_delete:
@@ -541,6 +548,19 @@ void f2fs_evict_inode(struct inode *inode)
stat_dec_inline_dir(inode);
stat_dec_inline_inode(inode);
+ if (unlikely(is_inode_flag_set(inode, FI_DIRTY_INODE))) {
+ sb_start_intwrite(inode->i_sb);
+ update_inode_page(inode);
+ if (is_inode_flag_set(inode, FI_DIRTY_INODE)) {
+ f2fs_inode_synced(inode);
+ f2fs_msg(sbi->sb, KERN_WARNING,
+ "inode info is inconsistent since "
+ "inode evicts before we writeback it");
+ }
+ sb_end_intwrite(inode->i_sb);
+ f2fs_bug_on(sbi, 1);
+ }
+
if (likely(!is_set_ckpt_flags(sbi, CP_ERROR_FLAG)))
f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE));
else
--
1.9.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2017-11-07 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 2:23 Yunlei He [this message]
2017-11-07 2:54 ` [PATCH] f2fs: avoid endless loop in funtion f2fs_sync_inode_meta 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=1510021438-23206-1-git-send-email-heyunlei@huawei.com \
--to=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=ning.jia@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).