linux-kernel - Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86

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: <Pine.LNX.4.64.0711301019590.1743@schroedinger.engr.sgi.com>
Date:	Fri, 30 Nov 2007 10:24:01 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on
 x86_64

On Fri, 30 Nov 2007, Ingo Molnar wrote:

> you mean this single patch:
> 
>  modules-fold-percpu_modcopy-into-modulec-and-get-rid-of-the-macro-from-hell.patch
> 
> that's the only patch i missed AFAICS.

That is a pretty uncritical one. Then there is the fix of the zero address 
handling in modules.c, the fixup for the use of __per_cpu_xx variables in 
modules.c. etc.

It would be best to test against mm since there are core changes here that 
will have to wait to the next merge period.

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