linux-kernel - Re: [PATCH 06/12] jump label v10: convert jump label to use a key

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 Jul 2010 13:37:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jbaron@...hat.com
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	mathieu.desnoyers@...ymtl.ca, hpa@...or.com, tglx@...utronix.de,
	rostedt@...dmis.org, andi@...stfloor.org, roland@...hat.com,
	rth@...hat.com, mhiramat@...hat.com, fweisbec@...il.com,
	avi@...hat.com, vgoyal@...hat.com, sam@...nborg.org,
	tony@...eyournoodle.com
Subject: Re: [PATCH 06/12] jump label v10: convert jump label to use a key

From: Jason Baron <jbaron@...hat.com>
Date: Tue, 27 Jul 2010 16:54:32 -0400

> Convert the jump label code to use a key to identify each related set of
> jump labels instead of a string. This saves space since we no longer need
> to store strings and their pointers, just the keys. In addition we can
> simplify the JUMP_LABEL macro to 2 arguments from 3. We use the address
> of the conditional variable as the key value. If jump labels are not enabled
> then we can use the conditional variable as usual.
> 
> Signed-off-by: Jason Baron <jbaron@...hat.com>

It doesn't make any sense to present these changes like this.

If the final implementation of the jump label entries uses this new
key based scheme, well that's what should be in the first patch of
this series which adds the basic jump label infrastructure.

As it is, it's just commit noise.
--
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/