From: kernel test robot <lkp@intel.com>
To: "qiwu.chen" <qiwuchen55@gmail.com>,
rostedt@goodmis.org, mhiramat@kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org, david@kernel.org,
mhocko@kernel.org, willy@infradead.org
Cc: oe-kbuild-all@lists.linux.dev,
linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org,
"qiwu.chen" <qiwu.chen@transsion.com>
Subject: Re: [PATCH v2] mm: vmscan: rework lru_shrink and write_folio tracepoints
Date: Wed, 13 May 2026 09:19:07 +0800 [thread overview]
Message-ID: <202605130942.9wJFWm9M-lkp@intel.com> (raw)
In-Reply-To: <20260506083652.100160-1-qiwu.chen@transsion.com>
Hi qiwu.chen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v7.1-rc3]
[cannot apply to akpm-mm/mm-everything trace/for-next next-20260508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/qiwu-chen/mm-vmscan-rework-lru_shrink-and-write_folio-tracepoints/20260513-040720
base: linus/master
patch link: https://lore.kernel.org/r/20260506083652.100160-1-qiwu.chen%40transsion.com
patch subject: [PATCH v2] mm: vmscan: rework lru_shrink and write_folio tracepoints
config: xtensa-randconfig-001-20260513 (https://download.01.org/0day-ci/archive/20260513/202605130942.9wJFWm9M-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605130942.9wJFWm9M-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/202605130942.9wJFWm9M-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/trace/define_trace.h:132,
from include/trace/events/vmscan.h:602,
from mm/vmscan.c:72:
include/trace/events/vmscan.h: In function 'trace_raw_output_mm_vmscan_write_folio':
include/trace/events/vmscan.h:358:12: warning: format '%p' expects argument of type 'void *', but argument 3 has type 'long unsigned int' [-Wformat=]
TP_printk("folio=%p lru=%s",
^~~~~~~~~~~~~~~~~
include/trace/trace_events.h:219:27: note: in definition of macro 'DECLARE_EVENT_CLASS'
trace_event_printf(iter, print); \
^~~~~
include/trace/trace_events.h:45:9: note: in expansion of macro 'PARAMS'
PARAMS(print)); \
^~~~~~
include/trace/events/vmscan.h:342:1: note: in expansion of macro 'TRACE_EVENT'
TRACE_EVENT(mm_vmscan_write_folio,
^~~~~~~~~~~
include/trace/events/vmscan.h:358:2: note: in expansion of macro 'TP_printk'
TP_printk("folio=%p lru=%s",
^~~~~~~~~
In file included from include/trace/trace_events.h:256,
from include/trace/define_trace.h:132,
from include/trace/events/vmscan.h:602,
from mm/vmscan.c:72:
include/trace/events/vmscan.h:358:20: note: format string is defined here
TP_printk("folio=%p lru=%s",
~^
%ld
In file included from include/trace/define_trace.h:132,
from include/trace/events/vmscan.h:602,
from mm/vmscan.c:72:
include/trace/events/vmscan.h: In function 'do_trace_event_raw_event_mm_vmscan_write_folio':
>> include/trace/events/vmscan.h:354:18: warning: assignment to 'long unsigned int' from 'struct folio *' makes integer from pointer without a cast [-Wint-conversion]
__entry->folio = folio;
^
include/trace/trace_events.h:427:4: note: in definition of macro '__DECLARE_EVENT_CLASS'
{ assign; } \
^~~~~~
include/trace/trace_events.h:435:9: note: in expansion of macro 'PARAMS'
PARAMS(assign), PARAMS(print)) \
^~~~~~
include/trace/trace_events.h:40:2: note: in expansion of macro 'DECLARE_EVENT_CLASS'
DECLARE_EVENT_CLASS(name, \
^~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:44:9: note: in expansion of macro 'PARAMS'
PARAMS(assign), \
^~~~~~
include/trace/events/vmscan.h:342:1: note: in expansion of macro 'TRACE_EVENT'
TRACE_EVENT(mm_vmscan_write_folio,
^~~~~~~~~~~
include/trace/events/vmscan.h:353:2: note: in expansion of macro 'TP_fast_assign'
TP_fast_assign(
^~~~~~~~~~~~~~
vim +354 include/trace/events/vmscan.h
343
344 TP_PROTO(struct folio *folio),
345
346 TP_ARGS(folio),
347
348 TP_STRUCT__entry(
349 __field(unsigned long, folio)
350 __field(int, lru)
351 ),
352
353 TP_fast_assign(
> 354 __entry->folio = folio;
355 __entry->lru = folio_lru_list(folio);
356 ),
357
358 TP_printk("folio=%p lru=%s",
359 __entry->folio,
360 __print_symbolic(__entry->lru, LRU_NAMES))
361 );
362
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-13 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 8:36 [PATCH v2] mm: vmscan: rework lru_shrink and write_folio tracepoints qiwu.chen
2026-05-08 23:47 ` Andrew Morton
2026-05-10 0:27 ` chenqiwu
2026-05-09 1:29 ` Andrew Morton
2026-05-10 0:36 ` chenqiwu
2026-05-13 0:45 ` kernel test robot
2026-05-13 1:19 ` kernel test robot [this message]
2026-05-13 3:04 ` kernel test robot
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=202605130942.9wJFWm9M-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mhocko@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qiwu.chen@transsion.com \
--cc=qiwuchen55@gmail.com \
--cc=rostedt@goodmis.org \
--cc=willy@infradead.org \
/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.