linux-kernel - Re: TRACE_BRANCH_PROFILING breaks gcc warnings

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:	Wed, 15 Apr 2009 09:46:59 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <srostedt@...hat.com>,
	Johannes Berg <johannes@...solutions.net>,
	Ingo Molnar <mingo@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: TRACE_BRANCH_PROFILING breaks gcc warnings

> > 
> > This has been mentioned before, and I've asked about sending a 
> > patch that would prevent TRACE_BRANCH_PROFILING from being 
> > selected with an allyesconfig.
> > 
> > It is easy to do. I could make it a selection and not a boolean 
> > and it will not select it as default, even for allyes/modconfig

We should have a symbol that is only set for allyesconfig builds.

Then we could do something like:

config TRACE_BRANCH_PROFILING
	depends on !ALLYESCONFIG

The advantage is that it is obvious why we have defiend
it like this rather than some inverse symbols.

I looked at generating such symbol in kconfig long time
ago but never finished it.

	Sam
--
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/