From: Herbert Xu Subject: Re: [PATCH] Export symbol ksize() Date: Thu, 12 Feb 2009 18:43:49 +0800 Message-ID: <20090212104349.GA13859@gondor.apana.org.au> References: <1234272104-10211-1-git-send-email-kirill@shutemov.name> <84144f020902100535i4d626a9fj8cbb305120cf332a@mail.gmail.com> <20090210134651.GA5115@epbyminw8406h.minsk.epam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Kirill A. Shutemov" , Christoph Lameter , Matt Mackall , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-crypto@vger.kernel.org, Geert.Uytterhoeven@sonycom.com To: Pekka J Enberg Return-path: Received: from rhun.apana.org.au ([64.62.148.172]:45103 "EHLO arnor.apana.org.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756355AbZBLKoT (ORCPT ); Thu, 12 Feb 2009 05:44:19 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: On Tue, Feb 10, 2009 at 04:06:53PM +0200, Pekka J Enberg wrote: > > Herbert, what do you think of this (untested) patch? Alternatively, we > could do something like kfree_secure() but it seems overkill for this one > call-site. I don't understand why you want to limit the use of ksize. If kmalloc is reserving more memory than what the user is asking for, then we should let them know the exact amount so that the extra bits aren't wasted. The only way to do that is through ksize. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt