Linux Trace Kernel
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Steven Rostedt <rostedt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	 Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	 Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	 John Ogness <john.ogness@linutronix.de>,
	Thomas Gleixner <tglx@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Julia Lawall <julia.lawall@inria.fr>,
	 Yury Norov <yury.norov@gmail.com>,
	regressions@lists.linux.dev
Subject: Re: [PATCH v3 2/2] tracing: Remove trace_printk.h from kernel.h
Date: Thu, 2 Jul 2026 15:43:14 +0200	[thread overview]
Message-ID: <akZpICZ0pGqspV2u@monoceros> (raw)
In-Reply-To: <20260624081948.301578807@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 4294 bytes --]

Hello,

On Wed, Jun 24, 2026 at 04:18:08AM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
> 
> There have been complaints about trace_printk.h causing more build time
> for being in kernel.h. Move it out of kernel.h and place it in the headers
> and C files that use it.
> 
> Link: https://lore.kernel.org/all/CAHk-=wikCBeVFjVXiY4o-oepdbjAoir5+TcAgtL12c4u1TpZLQ@mail.gmail.com/
> 
> Suggested-by: Yury Norov <yury.norov@gmail.com>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

This patch became commit 9cbc3d9806d3 ("tracing: Remove trace_printk.h
from kernel.h") that currently is in next via

	https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git trace/fixes

.

It creates a build regression for an ARCH=arc allmodconfig build:

	  CC      lib/test_context-analysis.o
	In file included from include/linux/local_lock_internal.h:8,
			 from include/linux/local_lock.h:5,
			 from lib/test_context-analysis.c:9:
	include/linux/local_lock_internal.h: In function ‘local_lock_acquire’:
	include/linux/lockdep.h:541:87: error: ‘_THIS_IP_’ undeclared (first use in this function)
	  541 | l)                     lock_acquire_exclusive(l, 0, 0, NULL, _THIS_IP_)
	      |                                                              ^~~~~~~~~
	include/linux/lockdep.h:509:88: note: in definition of macro ‘lock_acquire_exclusive’
	  509 | re_exclusive(l, s, t, n, i)           lock_acquire(l, s, t, 0, 1, n, i)
	      |                                                                      ^
	include/linux/local_lock_internal.h:46:9: note: in expansion of macro ‘lock_map_acquire’
	   46 |         lock_map_acquire(&l->dep_map);
	      |         ^~~~~~~~~~~~~~~~
	include/linux/lockdep.h:541:87: note: each undeclared identifier is reported only once for each function it appears in
	  541 | l)                     lock_acquire_exclusive(l, 0, 0, NULL, _THIS_IP_)
	      |                                                              ^~~~~~~~~
	include/linux/lockdep.h:509:88: note: in definition of macro ‘lock_acquire_exclusive’
	  509 | re_exclusive(l, s, t, n, i)           lock_acquire(l, s, t, 0, 1, n, i)
	      |                                                                      ^
	include/linux/local_lock_internal.h:46:9: note: in expansion of macro ‘lock_map_acquire’
	   46 |         lock_map_acquire(&l->dep_map);
	      |         ^~~~~~~~~~~~~~~~
	include/linux/local_lock_internal.h: In function ‘local_trylock_acquire’:
	include/linux/lockdep.h:542:87: error: ‘_THIS_IP_’ undeclared (first use in this function)
	  542 | try(l)                 lock_acquire_exclusive(l, 0, 1, NULL, _THIS_IP_)
	      |                                                              ^~~~~~~~~
	include/linux/lockdep.h:509:88: note: in definition of macro ‘lock_acquire_exclusive’
	  509 | re_exclusive(l, s, t, n, i)           lock_acquire(l, s, t, 0, 1, n, i)
	      |                                                                      ^
	include/linux/local_lock_internal.h:53:9: note: in expansion of macro ‘lock_map_acquire_try’
	   53 |         lock_map_acquire_try(&l->dep_map);
	      |         ^~~~~~~~~~~~~~~~~~~~
	include/linux/local_lock_internal.h: In function ‘local_lock_release’:
	include/linux/lockdep.h:545:65: error: ‘_THIS_IP_’ undeclared (first use in this function)
	  545 | fine lock_map_release(l)                     lock_release(l, _THIS_IP_)
	      |                                                              ^~~~~~~~~
	include/linux/local_lock_internal.h:62:9: note: in expansion of macro ‘lock_map_release’
	   62 |         lock_map_release(&l->dep_map);
	      |         ^~~~~~~~~~~~~~~~
	make[5]: *** [scripts/Makefile.build:289: lib/test_context-analysis.o] Error 1
	make[4]: *** [scripts/Makefile.build:549: lib] Error 2
	make[3]: *** [Makefile:2184: .] Error 2
	make[2]: *** [Makefile:372: __build_one_by_one] Error 2
	make[1]: *** [Makefile:248: __sub-make] Error 2
	make[1]: Leaving directory '/home/uwe/work/kbuild/arc'
	make: *** [Makefile:248: __sub-make] Error 2

#regzbot introduced: 9cbc3d9806d3

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2026-07-02 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  8:18 [PATCH v3 0/2] tracing: Remove trace_printk.h from kernel.h Steven Rostedt
2026-06-24  8:18 ` [PATCH v3 1/2] tracing: Move non-trace_printk prototypes into trace_controls.h Steven Rostedt
2026-06-24  8:18 ` [PATCH v3 2/2] tracing: Remove trace_printk.h from kernel.h Steven Rostedt
2026-06-24 10:11   ` David Laight
2026-06-24 14:32     ` Steven Rostedt
2026-06-24 15:48       ` David Laight
2026-07-02 13:43   ` Uwe Kleine-König [this message]
2026-07-02 20:57     ` Steven Rostedt
2026-06-25  7:56 ` [PATCH v3 0/2] " Sebastian Andrzej Siewior

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=akZpICZ0pGqspV2u@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=john.ogness@linutronix.de \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=regressions@lists.linux.dev \
    --cc=rostedt@kernel.org \
    --cc=tglx@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yury.norov@gmail.com \
    /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