From: kernel test robot <lkp@intel.com>
To: Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chao:bugfix/common 5/5] include/trace/events/f2fs.h:2655:19: warning: format '%lld' expects argument of type 'long long int', but argument 6 has type 'long unsigned int'
Date: Tue, 17 Mar 2026 20:46:55 +0100 [thread overview]
Message-ID: <202603172038.fCcFKBQE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
head: c85deae607667bb160a277e75324a45879161285
commit: c85deae607667bb160a277e75324a45879161285 [5/5] f2fs: introduce trace_f2fs_map_lock()
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260317/202603172038.fCcFKBQE-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260317/202603172038.fCcFKBQE-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/202603172038.fCcFKBQE-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/trace/define_trace.h:132,
from include/trace/events/f2fs.h:2665,
from fs/f2fs/super.c:41:
include/trace/events/f2fs.h: In function 'trace_raw_output_f2fs_map_lock':
>> include/trace/events/f2fs.h:2655:19: warning: format '%lld' expects argument of type 'long long int', but argument 6 has type 'long unsigned int' [-Wformat=]
2655 | TP_printk("dev = (%d,%d), ino = %lu, index = %lld, flag = %d, %s",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:219:34: note: in definition of macro 'DECLARE_EVENT_CLASS'
219 | trace_event_printf(iter, print); \
| ^~~~~
include/trace/trace_events.h:45:30: note: in expansion of macro 'PARAMS'
45 | PARAMS(print)); \
| ^~~~~~
include/trace/events/f2fs.h:2633:1: note: in expansion of macro 'TRACE_EVENT'
2633 | TRACE_EVENT(f2fs_map_lock,
| ^~~~~~~~~~~
include/trace/events/f2fs.h:2655:9: note: in expansion of macro 'TP_printk'
2655 | TP_printk("dev = (%d,%d), ino = %lu, index = %lld, flag = %d, %s",
| ^~~~~~~~~
In file included from include/trace/trace_events.h:256:
include/trace/events/f2fs.h:2655:57: note: format string is defined here
2655 | TP_printk("dev = (%d,%d), ino = %lu, index = %lld, flag = %d, %s",
| ~~~^
| |
| long long int
| %ld
vim +2655 include/trace/events/f2fs.h
2634
2635 TP_PROTO(struct inode *inode, pgoff_t index, int flag, char *string),
2636
2637 TP_ARGS(inode, index, flag, string),
2638
2639 TP_STRUCT__entry(
2640 __field(dev_t, dev)
2641 __field(ino_t, ino)
2642 __field(pgoff_t, index)
2643 __field(int, flag)
2644 __field(char *, string)
2645 ),
2646
2647 TP_fast_assign(
2648 __entry->dev = inode->i_sb->s_dev;
2649 __entry->ino = inode->i_ino;
2650 __entry->index = index;
2651 __entry->flag = flag;
2652 __entry->string = string;
2653 ),
2654
> 2655 TP_printk("dev = (%d,%d), ino = %lu, index = %lld, flag = %d, %s",
2656 show_dev_ino(__entry),
2657 __entry->index,
2658 __entry->flag,
2659 __entry->string)
2660 );
2661
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-17 19:47 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=202603172038.fCcFKBQE-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.