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, 16 Mar 2012 14:32:27 -0700 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Seth Jennings <sjenning@...ux.vnet.ibm.com> Cc: Dan Magenheimer <dan.magenheimer@...cle.com>, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, Nitin Gupta <ngupta@...are.org>, Robert Jennings <rcj@...ux.vnet.ibm.com>, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH] staging: zsmalloc: add user-definable alloc/free funcs On Fri, Mar 16, 2012 at 04:04:48PM -0500, Seth Jennings wrote: > This patch allows a zsmalloc user to define the page > allocation and free functions to be used when growing > or releasing parts of the memory pool. > > The functions are passed in the struct zs_pool_ops parameter > of zs_create_pool() at pool creation time. If this parameter > is NULL, zsmalloc uses alloc_page and __free_page() by default. > > While there is no current user of this functionality, zcache > development plans to make use of it in the near future. I'm starting to get tired of seeing new features be added to this chunk of code, and the other related bits, without any noticable movement toward getting it merged into the mainline tree. So, I'm going to take a stance here and say, no more new features until it gets merged into the "real" part of the kernel tree, as you all should not be spinning your wheels on new stuff, when there's no guarantee that the whole thing could just be rejected outright tomorrow. I'm sorry, I know this isn't fair for your specific patch, but we have to stop this sometime, and as this patch adds code isn't even used by anyone, its a good of a time as any. greg k-h -- 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