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
| ||
|
Date: Sun, 20 Sep 2009 13:12:08 +0300 From: Pekka Enberg <penberg@...helsinki.fi> To: Tejun Heo <tj@...nel.org> CC: Mel Gorman <mel@....ul.ie>, Nick Piggin <npiggin@...e.de>, Christoph Lameter <cl@...ux-foundation.org>, heiko.carstens@...ibm.com, sachinp@...ibm.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH 1/3] slqb: Do not use DEFINE_PER_CPU for per-node data Tejun Heo wrote: > Pekka Enberg wrote: >> On Fri, Sep 18, 2009 at 10:34 PM, Mel Gorman <mel@....ul.ie> wrote: >>> SLQB used a seemingly nice hack to allocate per-node data for the statically >>> initialised caches. Unfortunately, due to some unknown per-cpu >>> optimisation, these regions are being reused by something else as the >>> per-node data is getting randomly scrambled. This patch fixes the >>> problem but it's not fully understood *why* it fixes the problem at the >>> moment. >> Ouch, that sounds bad. I guess it's architecture specific bug as x86 >> works ok? Lets CC Tejun. > > Is the corruption being seen on ppc or s390? On ppc. -- 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/
Powered by blists - more mailing lists