From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: allocinfo_ioctl_test.c:92:73: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'}
Date: Thu, 09 Jul 2026 10:52:01 +0200 [thread overview]
Message-ID: <202607091033.chvdX3bF-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Abhishek Bapat <abhishekbapat@google.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Abhishek-Bapat/alloc_tag-add-ioctl-to-proc-allocinfo/20260709-020518
head: ce2ea00e2482d8be7ac83d783dc4858153731c55
commit: 178d595eded89e9321a6349cb0a419e50315105b kselftest: alloc_tag: add kselftest for ioctl interface
date: 15 hours ago
:::::: branch date: 15 hours ago
:::::: commit date: 15 hours ago
config: powerpc64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260709/202607091033.chvdX3bF-lkp@intel.com/config)
compiler: powerpc64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607091033.chvdX3bF-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/r/202607091033.chvdX3bF-lkp@intel.com/
All warnings (new ones prefixed by >>):
allocinfo_ioctl_test.c: In function 'match_entries':
>> allocinfo_ioctl_test.c:92:73: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
92 | ksft_print_msg("Entry count mismatch. ioctl entries: %llu, proc entries: %llu\n",
| ~~~^
| |
| long long unsigned int
| %lu
93 | tags->count, procfs_entries->count);
| ~~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
allocinfo_ioctl_test.c:92:93: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
92 | ksft_print_msg("Entry count mismatch. ioctl entries: %llu, proc entries: %llu\n",
| ~~~^
| |
| long long unsigned int
| %lu
93 | tags->count, procfs_entries->count);
| ~~~~~~~~~~~~~~~~~~~~~
| |
| __u64 {aka long unsigned int}
allocinfo_ioctl_test.c:100:44: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
100 | ksft_print_msg("%lluth entry does not match.\n", i);
| ~~~^ ~
| | |
| long long unsigned int __u64 {aka long unsigned int}
| %lu
allocinfo_ioctl_test.c: In function 'get_filtered_procfs_entries':
allocinfo_ioctl_test.c:140:44: warning: format '%llu' expects argument of type 'long long unsigned int *', but argument 3 has type '__u64 *' {aka 'long unsigned int *'} [-Wformat=]
140 | matches = sscanf(line, "%llu %llu %[^:]:%llu func:%s",
| ~~~^
| |
| long long unsigned int *
| %lu
141 | &procfs_entry.counter.bytes,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| __u64 * {aka long unsigned int *}
allocinfo_ioctl_test.c:140:49: warning: format '%llu' expects argument of type 'long long unsigned int *', but argument 4 has type '__u64 *' {aka 'long unsigned int *'} [-Wformat=]
140 | matches = sscanf(line, "%llu %llu %[^:]:%llu func:%s",
| ~~~^
| |
| long long unsigned int *
| %lu
141 | &procfs_entry.counter.bytes,
142 | &procfs_entry.counter.calls,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| __u64 * {aka long unsigned int *}
allocinfo_ioctl_test.c:140:60: warning: format '%llu' expects argument of type 'long long unsigned int *', but argument 6 has type '__u64 *' {aka 'long unsigned int *'} [-Wformat=]
140 | matches = sscanf(line, "%llu %llu %[^:]:%llu func:%s",
| ~~~^
| |
| long long unsigned int *
| %lu
......
144 | &procfs_entry.tag.lineno,
| ~~~~~~~~~~~~~~~~~~~~~~~~
| |
| __u64 * {aka long unsigned int *}
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-09 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607091033.chvdX3bF-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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