linux-kernel - [PATCH v4 0/8] ring-buffer/tracing: Save module information in persistent memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250305164539.379008535@goodmis.org> (raw)
Date: Fri, 14 Mar 2025 09:59:04 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: rostedt@...dmis.org,
	linux-kernel@...r.kernel.org,
	linux-trace-kernel@...r.kernel.org
Cc: akpm@...ux-foundation.org,
	mark.rutland@....com,
	mathieu.desnoyers@...icios.com,
	mhiramat@...nel.org,
	biju.das.jz@...renesas.com
Subject: [PATCH v4 0/8] ring-buffer/tracing: Save module information in persistent memory

From: Steven Rostedt <rostedt@...dmis.org>


> This updates the persistent instance to record what modules were
> loaded and what addresses they were loaded at.



This series is giving build error on linux-next for 2 days(next-20250314
and next-20250313) on Renesas RZ/G3E SMARC EVK platform (ARM64)

Reverting trace related commits fixes the build issue.

build-errors:
kernel/trace/trace.c: In function ‘save_mod’:
kernel/trace/trace.c:6041:45: error: invalid use of undefined type ‘struct module’
 6041 |         entry->mod_addr = (unsigned long)mod->mem[MOD_TEXT].base;
      |                                             ^~
  CC      net/ethtool/phc_vclocks.o
kernel/trace/trace.c:6041:51: error: ‘MOD_TEXT’ undeclared (first use in this function)
 6041 |         entry->mod_addr = (unsigned long)mod->mem[MOD_TEXT].base;
      |                                                   ^~~~~~~~
kernel/trace/trace.c:6041:51: note: each undeclared identifier is reported only once for each function it appears in
  CC      fs/proc/cpuinfo.o