From: Chao Yu <chao@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
patches@lists.linux.dev
Subject: Re: [PATCH] f2fs: Fix format specifier in sanity_check_inode()
Date: Wed, 22 Jan 2025 14:27:14 +0800 [thread overview]
Message-ID: <bef8db0a-f2ef-4aea-ab19-c3390f7bf93e@kernel.org> (raw)
In-Reply-To: <20250120-f2fs-fix-wformat-min_inline_xattr_size-v1-1-508cac1474fe@kernel.org>
On 1/20/25 20:59, Nathan Chancellor wrote:
> When building for 32-bit platforms, for which 'size_t' is 'unsigned int',
> there is a warning due to an incorrect format specifier:
>
> fs/f2fs/inode.c:320:6: error: format specifies type 'unsigned long' but the argument has type 'unsigned int' [-Werror,-Wformat]
> 318 | f2fs_warn(sbi, "%s: inode (ino=%lx) has corrupted i_inline_xattr_size: %d, min: %lu, max: %lu",
> | ~~~
> | %u
> 319 | __func__, inode->i_ino, fi->i_inline_xattr_size,
> 320 | MIN_INLINE_XATTR_SIZE, MAX_INLINE_XATTR_SIZE);
> | ^~~~~~~~~~~~~~~~~~~~~
> fs/f2fs/f2fs.h:1855:46: note: expanded from macro 'f2fs_warn'
> 1855 | f2fs_printk(sbi, false, KERN_WARNING fmt, ##__VA_ARGS__)
> | ~~~ ^~~~~~~~~~~
> fs/f2fs/xattr.h:86:31: note: expanded from macro 'MIN_INLINE_XATTR_SIZE'
> 86 | #define MIN_INLINE_XATTR_SIZE (sizeof(struct f2fs_xattr_header) / sizeof(__le32))
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Use the format specifier for 'size_t', '%zu', to resolve the warning.
>
> Fixes: 5c1768b67250 ("f2fs: fix to do sanity check correctly on i_inline_xattr_size")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2025-01-22 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 12:59 [PATCH] f2fs: Fix format specifier in sanity_check_inode() Nathan Chancellor
2025-01-21 17:00 ` [f2fs-dev] " patchwork-bot+f2fs
2025-01-22 6:27 ` Chao Yu [this message]
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=bef8db0a-f2ef-4aea-ab19-c3390f7bf93e@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
/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