linux-kernel - Re: [PATCH] tracing: fix a build error on alpha and m68k

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]

Date:	Thu, 23 Oct 2008 18:51:35 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Alexey Dobriyan" <adobriyan@...il.com>,
	"Geert Uytterhoeven" <geert@...ux-m68k.org>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Steven Rostedt" <rostedt@...dmis.org>
Subject: Re: [PATCH] tracing: fix a build error on alpha and m68k

2008/10/23 Ingo Molnar <mingo@...e.hu>:
> hm, zapped the commit then.
>
> the problem is most likely that none of these architectures is lockdep
> enabled, hence they have no irqtrace wrappers, hence not all of the
> tracers can be built on them?
>
>        Ingo
>

But they should be able to use the tracing for several other tracers.
One other problem is that you need CONFIG_TRACE_IRQFLAGS (is that a
lockdep or just trace feature?) to use any tracer since the
tracing_cpumask file is always created for all tracer. This file has
tracing_cpumask_write() as a write operation, and this func uses
raw_local_funcs....

Perhaps we should disable the tracing_cpu_mask related things if
TRACE_IRQFLAGS in not configured?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/