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: Wed, 7 May 2008 13:30:39 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Andrew Morton <akpm@...ux-foundation.org> cc: Andrea Arcangeli <andrea@...ranet.com>, clameter@....com, steiner@....com, holt@....com, npiggin@...e.de, a.p.zijlstra@...llo.nl, kvm-devel@...ts.sourceforge.net, kanojsarcar@...oo.com, rdreier@...co.com, swise@...ngridcomputing.com, linux-kernel@...r.kernel.org, avi@...ranet.com, linux-mm@...ck.org, general@...ts.openfabrics.org, hugh@...itas.com, rusty@...tcorp.com.au, aliguori@...ibm.com, chrisw@...hat.com, marcelo@...ck.org, dada1@...mosbay.com, paulmck@...ibm.com Subject: Re: [PATCH 01 of 11] mmu-notifier-core On Wed, 7 May 2008, Andrew Morton wrote: > > The patch looks OK to me. As far as I can tell, authorship has been destroyed by at least two of the patches (ie Christoph seems to be the author, but Andrea seems to have dropped that fact). > The proposal is that we sneak this into 2.6.26. Are there any > sufficiently-serious objections to this? Yeah, too late and no upside. That "locking" code is also too ugly to live, at least without some serious arguments for why it has to be done that way. Sorting the locks? In a vmalloc'ed area? And calling this something innocuous like "mm_lock()"? Hell no. That code needs some serious re-thinking. 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