From: Manfred Spraul <manfred@colorfullife.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@osdl.org>,
"Kevin O'Connor" <kevin@koconnor.net>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Size-128 slab leak
Date: Fri, 03 Feb 2006 07:21:27 +0100 [thread overview]
Message-ID: <43E2F667.8020404@colorfullife.com> (raw)
In-Reply-To: <84144f020602012332g57a58f0aw373983fc6bc7368b@mail.gmail.com>
Pekka Enberg wrote:
>We already have last caller in dbg_userword. Manfred, is there a
>reason we're not using it?
>
>
>
IIRC only due to historical reasons: dbg_userword is newer than this patch.
--
Manfred
next prev parent reply other threads:[~2006-02-03 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 2:49 Size-128 slab leak Kevin O'Connor
2006-02-02 7:10 ` Andrew Morton
2006-02-02 7:32 ` Pekka Enberg
2006-02-03 6:21 ` Manfred Spraul [this message]
2006-02-03 4:00 ` Kevin O'Connor
2006-02-03 13:21 ` Stephen Smalley
2006-02-03 15:13 ` James Morris
2006-02-04 1:13 ` Kevin O'Connor
2006-02-14 4:52 ` Jeffrey Mahoney
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=43E2F667.8020404@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=kevin@koconnor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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