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: Fri, 21 Nov 2014 16:18:56 -0800 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Tejun Heo <tj@...nel.org> Cc: Frederic Weisbecker <fweisbec@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Dave Jones <davej@...hat.com>, Don Zickus <dzickus@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, "the arch/x86 maintainers" <x86@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Andy Lutomirski <luto@...capital.net>, Arnaldo Carvalho de Melo <acme@...stprotocols.net> Subject: Re: frequent lockups in 3.18rc4 On Fri, Nov 21, 2014 at 4:11 PM, Tejun Heo <tj@...nel.org> wrote: > > I don't think there's much percpu allocator itself can do. The > ability to grow dynamically comes from being able to allocate > relatively consistent layout among areas for different CPUs and pretty > much requires vmalloc area and it'd generally be a good idea to take > out the vmalloc fault anyway. Why do you guys worry so much about the vmalloc fault? This started because of a very different issue: putting the actual stack in vmalloc space. Then it can cause nasty triple faults etc. But the normal vmalloc fault? Who cares, really? If that causes problems, they are bugs. Fix them. Linus -- 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