| 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: Thu, 7 Jan 2010 21:00:34 -0800 (PST) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Arjan van de Ven <arjan@...radead.org> cc: Christoph Lameter <cl@...ux-foundation.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Peter Zijlstra <peterz@...radead.org>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, "minchan.kim@...il.com" <minchan.kim@...il.com>, "hugh.dickins" <hugh.dickins@...cali.co.uk>, Nick Piggin <nickpiggin@...oo.com.au>, Ingo Molnar <mingo@...e.hu> Subject: Re: [RFC][PATCH 6/8] mm: handle_speculative_fault() On Thu, 7 Jan 2010, Arjan van de Ven wrote: > > if an app has to change because our kernel sucks (for no good reason), > "change the app" really is the lame type of answer. Well, in all fairness, I doubt other kernels do any better. So changing the app is likely to help in general, and thus be at least part of the right solution. But as outlined, we _can_ almost certainly do better on many simple and common cases, so changing the kernel - in addition to fixing app memory allocation patterns - sounds like a good avenue. 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