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: <20071130183512.GA8985@elte.hu>
Date:	Fri, 30 Nov 2007 19:35:12 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Lameter <clameter@....com>
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


* Christoph Lameter <clameter@....com> wrote:

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

you again talk about modules.c but my test kernel that crashes has no 
modules at all.

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

if you treat testing and review efforts like that they might have to 
wait even longer :-( "My stuff is there somewhere amongst 1415 -mm 
patches. Thank you for your interest and buzz off already."

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