From: Arjan van de Ven <arjan@infradead.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: akpm@linux-foundation.org, clameter@sgi.com,
linux-kernel@vger.kernel.org, jsipek@fsl.cs.sunysb.edu,
unionfs@filesystems.org, bunk@stusta.de, hooanon05@yahoo.co.jp
Subject: Re: [PATCH 1/3] slab: introduce krealloc
Date: Wed, 21 Feb 2007 10:36:02 +0100 [thread overview]
Message-ID: <1172050562.3531.171.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <84144f020702210133k4a9f40f0mc0f51524fac9c524@mail.gmail.com>
On Wed, 2007-02-21 at 11:33 +0200, Pekka Enberg wrote:
> On 2/21/07, Arjan van de Ven <arjan@infradead.org> wrote:
> > please mark this one __must_check.. not storing realloc() return values
> > is one of the more nasty types of bugs... but gcc can help us greatly
> > here ;)
>
> So I guess we want the same thing for the other allocator functions
> (__kmalloc et al) as well?
kmalloc doesn't normally get forgotten. realloc() otoh is a very classic
and far more frequent mistake....
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2007-02-21 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 8:06 Pekka J Enberg
2007-02-21 9:24 ` Arjan van de Ven
2007-02-21 9:33 ` Pekka Enberg
2007-02-21 9:36 ` Arjan van de Ven [this message]
2007-02-21 17:51 ` Christoph Lameter
2007-02-21 17:53 ` Christoph Lameter
2007-02-21 18:21 ` Pekka Enberg
2007-02-21 18:27 ` Christoph Lameter
2007-02-21 18:37 ` Pekka Enberg
2007-02-21 18:48 ` Christoph Lameter
2007-02-21 19:19 ` Pekka Enberg
2007-02-21 19:22 ` Christoph Lameter
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=1172050562.3531.171.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=clameter@sgi.com \
--cc=hooanon05@yahoo.co.jp \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=unionfs@filesystems.org \
/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
all inboxes | Powered by JetHome®