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]

Message-ID: <c62985530810231025j69c38776q1244510bd7990c6f@mail.gmail.com>
Date:	Thu, 23 Oct 2008 19:25:10 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"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
Subject: Re: [PATCH] tracing: fix a build error on alpha and m68k

2008/10/23 Steven Rostedt <rostedt@...dmis.org>:
>
> On Thu, 23 Oct 2008, Fr?d?ric Weisbecker wrote:
>>
>> But to let the core trace.c to be built for other types of tracing,
>> the best thing I see is to put some ifdef CONFIG_TRACE_IRQFLAGS on the
>> tracing_cpumask functions and structure, and actually on the creation
>> of this file.
>
> Is there a reason that you use "raw_local_irq_disable" instead of
> local_irq_disable?


I'm not using anything :)
This is about the tracing_cpumask debugfs file implemented in trace.c
It's tracing_cpumask_write function uses the raw_local functions, I
guess because its locking doesn't need to be traced.
And the problem here is that some archs don't implement raw_local
functions and so trace.c doesn't compile with alpha or m68k.
But actually this file is not needed for them.
--
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/