linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	Christoph Lameter <cl@linux-foundation.org>,
	Matt Mackall <mpm@selenic.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-crypto@vger.kernel.org, Geert.Uytterhoeven@sonycom.com
Subject: Re: [PATCH] Export symbol ksize()
Date: Thu, 12 Feb 2009 12:45:21 +0200	[thread overview]
Message-ID: <1234435521.28812.165.camel@penberg-laptop> (raw)
In-Reply-To: <20090212104349.GA13859@gondor.apana.org.au>

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.

On Thu, 2009-02-12 at 18:43 +0800, Herbert Xu wrote:
> I don't understand why you want to limit the use of ksize.

Because the API was being widely abused in the nommu code, for example.
I'd rather not add it back for this special case which can be handled
otherwise.

			Pekka

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-02-12 10:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 13:21 Kirill A. Shutemov
2009-02-10 13:35 ` Pekka Enberg
2009-02-10 13:46   ` Kirill A. Shutemov
2009-02-10 14:06     ` Pekka J Enberg
2009-02-12 10:43       ` Herbert Xu
2009-02-12 10:45         ` Pekka Enberg [this message]
2009-02-12 10:50           ` Herbert Xu
2009-02-12 13:10             ` Nick Piggin
2009-02-12 23:09               ` Herbert Xu
2009-02-12 23:37                 ` Matt Mackall
2009-02-13 13:20                   ` Nick Piggin
2009-02-13 16:57                     ` Kyle Moffett
2009-02-12 15:55             ` Pekka Enberg
2009-02-12 23:09               ` Herbert Xu
2009-02-15 21:36               ` Andrew Morton
2009-02-15 21:43                 ` Matt Mackall
2009-02-15 21:55                   ` Andrew Morton
2009-02-15 23:49                     ` Matt Mackall
2009-02-16  1:00                       ` Andrew Morton
2009-02-16  1:21                         ` Herbert Xu
2009-02-16  1:28                           ` Matt Mackall
2009-02-16  1:52                             ` Herbert Xu
2009-02-16  1:54                               ` Matt Mackall
2009-02-16  1:57                                 ` Herbert Xu
2009-02-16  1:38                         ` Matt Mackall
2009-02-17  8:43                           ` Geert Uytterhoeven
2009-02-17 16:17                       ` Christoph Lameter
2009-02-17 17:03                         ` Pekka Enberg
2009-02-17 17:06                           ` Christoph Lameter
2009-02-16 13:56       ` Johannes Weiner
2009-02-16 14:09         ` Pekka Enberg
2009-02-16 16:32         ` Joe Perches
2009-02-16 17:29           ` Pekka Enberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1234435521.28812.165.camel@penberg-laptop \
    --to=penberg@cs.helsinki.fi \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=cl@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kirill@shutemov.name \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox