linux-kernel - Re: [PATCH 01/16] vmalloc: fix use of non-existent percpu variable in put_cpu

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: <4AD6E6F2.9060109@kernel.org>
Date:	Thu, 15 Oct 2009 18:10:10 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au,
	mingo@...hat.com, tglx@...utronix.de, akpm@...ux-foundation.org,
	rostedt@...dmis.org, hpa@...or.com, cebbert@...hat.com,
	Nick Piggin <npiggin@...e.de>
Subject: Re: [PATCH 01/16] vmalloc: fix use of non-existent percpu variable
 in put_cpu_var()

Christoph Lameter wrote:
> This looks like a candidate for 2.6.32.

Yeah, this could go to 2.6.32 too but it's only exposed by percpu
changes in percpu#for-next, so putting this together with related
percpu changes wouldn't be too bad either.  Does anyone feel strong
about this going in for 2.6.32?

Thanks.

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