linux-kernel - Re: [PATCH 00/10] jump label: introduce very

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: <1329926881.25686.111.camel@gandalf.stny.rr.com>
Date:	Wed, 22 Feb 2012 11:08:01 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jason Baron <jbaron@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	a.p.zijlstra@...llo.nl, mathieu.desnoyers@...icios.com,
	davem@...emloft.net, ddaney.cavm@...il.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 00/10] jump label: introduce very_[un]likely + cleanups
 + docs

On Wed, 2012-02-22 at 10:56 -0500, Jason Baron wrote:
> On Wed, Feb 22, 2012 at 10:54:03AM -0500, Steven Rostedt wrote:
> > On Wed, 2012-02-22 at 10:42 -0500, Jason Baron wrote:
> > 
> > > Do you have 'CONFIG_CC_OPTIMIZE_FOR_SIZE' set?
> > 
> > Yes I do :-p
> > 
> > But that's because the distro config I started with had it set too.
> > 
> > -- Steve
> > 
> > 
> 
> Right, with CONFIG_CC_OPTIMIZE_FOR_SIZE unset, which is the default, at
> least on x86, I have not seen a single case of the 'jmp;jmp'.
> 

What the config default is, is unimportant. It only maters to kernel
hackers that build our own kernels. What's important is what distros do.

On debian testing I have in config-3.0.0-1-amd64:

CONFIG_CC_OPTIMIZE_FOR_SIZE=y


Although it is not set on the latest fedora 16 config.

Someone should tell debian to turn it off.

-- Steve


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