linux-kernel - Re: [PATCH] trace: fix undefined tracing functions build error

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: <20171026065551.0e8126ba@vmware.local.home>
Date:   Thu, 26 Oct 2017 06:55:51 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Julien Thierry <julien.thierry@....com>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] trace: fix undefined tracing functions build error

On Thu, 26 Oct 2017 09:37:40 +0100
Julien Thierry <julien.thierry@....com> wrote:

> When selecting CONFIG_PREEMPTIRQ_EVENTS without CONFIG_DEBUG_PREEMPT,
> trace_preempt_(en|dis)able_* names do not get defined. This causes a build
> error in function trace_preempt_off (kernel/trace/trace_irqsoff.c) when
> CONFIG_PREEMPT_TRACER is enabled.
> 
> Similarly, when selecting CONFIG_PREEMPTIRQ_EVENTS and
> CONFIG_PROVE_LOCKING, trace_irq_(en|dis)able_* names do not get defined,
> although it seems they do not get referenced in that configuration.
> 
> Ensure trace_(irq|preempt)_* names are always defined, becoming empty
> macros in the cases where they were not defined previously.
> 

Thanks,

But I've seen another patch that I believe fixes this issue, but I'm
currently traveling in Prague, and attending several conferences there,
and haven't had time to look at my email.

When I get home next week I'll be applying patches sent to me.

Thanks,

-- Steve