From: Pekka J Enberg <penberg@cs.helsinki.fi>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: 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,
Herbert Xu <herbert@gondor.apana.org.au>,
Geert.Uytterhoeven@sonycom.com
Subject: Re: [PATCH] Export symbol ksize()
Date: Tue, 10 Feb 2009 16:06:53 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.64.0902101605070.20991@melkki.cs.Helsinki.FI> (raw)
In-Reply-To: <20090210134651.GA5115@epbyminw8406h.minsk.epam.com>
On Tue, Feb 10, 2009 at 03:35:03PM +0200, Pekka Enberg wrote:
> > We unexported ksize() because it's a problematic interface and you
> > almost certainly want to use the alternatives (e.g. krealloc). I think
> > I need bit more convincing to apply this patch...
On Tue, 10 Feb 2009, Kirill A. Shutemov wrote:
> It just a quick fix. If anybody knows better solution, I have no
> objections.
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.
Pekka
next prev parent reply other threads:[~2009-02-10 14:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 13:21 [PATCH] Export symbol ksize() 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 [this message]
2009-02-12 10:43 ` Herbert Xu
2009-02-12 10:45 ` Pekka Enberg
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=Pine.LNX.4.64.0902101605070.20991@melkki.cs.Helsinki.FI \
--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;
as well as URLs for NNTP newsgroup(s).