linux-kernel - Re: Jump Label initialization

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, 28 Sep 2011 22:28:54 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	jeremy@...p.org
Cc:	jbaron@...hat.com, peterz@...radead.org, rostedt@...dmis.org,
	linux-kernel@...r.kernel.org, michael@...erman.id.au,
	jang@...ux.vnet.ibm.com, ddaney@...iumnetworks.com
Subject: Re: Jump Label initialization

From: Jeremy Fitzhardinge <jeremy@...p.org>
Date: Wed, 28 Sep 2011 19:14:52 -0700

> I'm experimenting at the moment with a patch to allow
> jump_label_enable() to be called fairly early, and have that be
> respected by jump_label_init().  I'm doing this by replacing
> arch_jump_label_poke_text_early() with
> arch_jump_label_transform_early(), which shares most of its code with
> its non-early variant, except that it expects to run in a pre-SMP
> environment.
> 
> Does this seem plausible? (I haven't tested it yet.)

I have no objections to this.
--
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/