linux-kernel - Re: [PATCH 1/5] x86/jump-label: Use best default nops for inital jump label calls

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: <1327698014.22710.140.camel@gandalf.stny.rr.com>
Date:	Fri, 27 Jan 2012 16:00:14 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jason Baron <jbaron@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH 1/5] x86/jump-label: Use best default nops for inital
 jump label calls

On Fri, 2012-01-27 at 12:50 -0800, H. Peter Anvin wrote:
> On 01/27/2012 12:49 PM, Steven Rostedt wrote:
> > 
> > If not, at the very least, I'll add a comment (in the last patch) that
> > explains why we use our own "JUMP_LABEL_INIT_NOP" instead of
> > ASM_NOP5_ATOMIC.
> > 
> 
> Then at least use GENERIC_NOP5_ATOMIC instead of open-coding it.

OK, I can do that. Hehe, I looked for the x86_32 version, but it was so
obfuscated that I didn't find it. Thanks for pointing it out.

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