From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Cc: <oe-kbuild-all@lists.linux.dev>,
David Hildenbrand <david@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-new 279/310] memory-failure.c:275:49: warning: format specifies type 'unsigned long' but the argument has type '__fsword_t' (aka 'int')
Date: Fri, 23 Jan 2026 14:23:12 +0800 [thread overview]
Message-ID: <3116e4e5-c1cd-27e2-69b4-6bf0fc0347c6@huawei.com> (raw)
In-Reply-To: <20260122093240.ef007fed49c166ae5ff256c1@linux-foundation.org>
On 2026/1/23 1:32, Andrew Morton wrote:
> On Thu, 22 Jan 2026 12:00:08 +0100 kernel test robot <lkp@intel.com> wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
>> head: dc4fe40a11269aead253fa0beb098b00417b8694
>> commit: ce9b369feafe8c65aa134b0c8791bf7f19e463e2 [279/310] selftests/mm: add memory failure clean pagecache test
>> config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260122/202601221142.mDWA1ucw-lkp@intel.com/config)
>> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601221142.mDWA1ucw-lkp@intel.com/reproduce)
>>
>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/202601221142.mDWA1ucw-lkp@intel.com/
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> memory-failure.c:275:49: warning: format specifies type 'unsigned long' but the argument has type '__fsword_t' (aka 'int') [-Wformat]
>> 275 | SKIP(return, "unsupported filesystem :%lx\n", fs_type);
>> | ~~~ ^~~~~~~
>> | %x
>
> Thanks.
>
> I don't think we can rely upon libc's __fsword_t being `int' in all
> situations for all time?
>
> We could add the typecast but perhaps it's better to change
> get_fs_type() to return int?
Yes, changing get_fs_type() to return int looks good to me. Will do it in v3.
Thanks.
.
prev parent reply other threads:[~2026-01-23 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:00 kernel test robot
2026-01-22 17:32 ` Andrew Morton
2026-01-23 6:23 ` Miaohe Lin [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=3116e4e5-c1cd-27e2-69b4-6bf0fc0347c6@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@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