From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [RESEND PATCH] f2fs: Fix one GCC warning
Date: Mon, 22 Apr 2019 21:27:59 +0800 [thread overview]
Message-ID: <1555939679-57452-1-git-send-email-zhangshaokun@hisilicon.com> (raw)
fs/f2fs/node.c: In function ‘f2fs_remove_inode_page’:
fs/f2fs/node.c:1193:47: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘blkcnt_t {aka long long unsigned int}’ [-Wformat=]
"Inconsistent i_blocks, ino:%lu, iblocks:%lu",
~~^
%llu
inode->i_ino, inode->i_blocks);
~~~~~~~~~~~~~~~
Fixes: cdad635bd068 ("f2fs: fix to avoid panic in f2fs_remove_inode_page()")
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Shaokun Zhang <zhangshaokun@hisilicon.com>
---
fs/f2fs/node.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 22d21c546bf6..e15d0be729b4 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -1190,7 +1190,7 @@ int f2fs_remove_inode_page(struct inode *inode)
if (unlikely(inode->i_blocks != 0 && inode->i_blocks != 8)) {
f2fs_msg(F2FS_I_SB(inode)->sb, KERN_WARNING,
- "Inconsistent i_blocks, ino:%lu, iblocks:%lu",
+ "Inconsistent i_blocks, ino:%lu, iblocks:%llu",
inode->i_ino, inode->i_blocks);
set_sbi_flag(F2FS_I_SB(inode), SBI_NEED_FSCK);
}
--
2.7.4
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-04-22 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 13:27 Shaokun Zhang [this message]
2019-04-23 2:57 ` [RESEND PATCH] f2fs: Fix one GCC warning Chao Yu
2019-04-23 3:31 ` Zhangshaokun
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=1555939679-57452-1-git-send-email-zhangshaokun@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).