From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Adrian Bunk <bunk@stusta.de>,
Patrick Caulfield <pcaulfie@redhat.com>,
David Teigland <teigland@redhat.com>,
bluez-devel@lists.sourceforge.net,
Marcel Holtmann <marcel@holtmann.org>,
Jiri Kosina <jkosina@suse.cz>,
Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: 2.6.22-rc7: known regressions with patches v2
Date: Sat, 7 Jul 2007 16:38:43 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707071633320.31544@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707071557160.16503@schroedinger.engr.sgi.com>
On Sat, 7 Jul 2007, Christoph Lameter wrote:
>
> What are these functions "malloc" and "free"? Would be good if those
> would be using kmalloc_track_caller() so that we can figure out who called
> them.
There's not a lot of those around. Looks like it's probably one of
init/do_mounts_rd.c:static void __init *malloc(size_t size)
init/initramfs.c:static void __init *malloc(size_t size)
both of which exist just because those things include "lib/inflate.c".
It's probably do_mounts_rd.c, because initramfs.c defines malloc/free
before the #include, and I would have expected gcc to just inline them in
that case.
That's probably the right thign to do in do_mounts_rd.c too, rather than
adding any kmalloc_track_caller() stuff.
Linus
prev parent reply other threads:[~2007-07-07 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <468FBA20.8060509@googlemail.com>
[not found] ` <1183825391.3066.59.camel@shinybook.infradead.org>
[not found] ` <6bffcb0e0707070959m12ba9b66n8587605eb1f6c21e@mail.gmail.com>
2007-07-07 23:07 ` 2.6.22-rc7: known regressions with patches v2 Christoph Lameter
2007-07-07 23:38 ` Linus Torvalds [this message]
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=alpine.LFD.0.999.0707071633320.31544@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bunk@stusta.de \
--cc=clameter@sgi.com \
--cc=dtor@insightbb.com \
--cc=dwmw2@infradead.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=pcaulfie@redhat.com \
--cc=teigland@redhat.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