From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [SLUB 3/5] Validation of slabs (metadata and guard zones)
Date: Tue, 10 Apr 2007 20:08:24 -0700 [thread overview]
Message-ID: <20070410200824.d116bbfd.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0704101922280.17722@schroedinger.engr.sgi.com>
On Tue, 10 Apr 2007 19:24:00 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
> SLUB contains a complicated section with #ifdef CONFIG_KALLSYSM and yadda
> dadda. Remove that and replace with __print_symbol.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> Index: linux-2.6.21-rc6/mm/slub.c
> ===================================================================
> --- linux-2.6.21-rc6.orig/mm/slub.c 2007-04-10 19:21:29.000000000 -0700
> +++ linux-2.6.21-rc6/mm/slub.c 2007-04-10 19:21:51.000000000 -0700
> @@ -290,27 +290,11 @@ static void init_tracking(struct kmem_ca
>
> static void print_track(const char *s, struct track *t)
> {
> -#ifdef CONFIG_KALLSYMS
> - char *modname;
> - const char *name;
> - unsigned long offset, size;
> - char namebuf[KSYM_NAME_LEN + 1];
> -#endif
> -
> if (!t->addr)
> return;
>
> -#ifdef CONFIG_KALLSYMS
> - name = kallsyms_lookup((unsigned long)t->addr, &size, &offset,
> - &modname, namebuf);
> -
> - if (name) {
> - printk(KERN_ERR "%s: %s+%#lx/%#lx", s, name, offset, size);
> - if (modname)
> - printk(" [%s]", modname);
> - } else
> -#endif
> - printk(KERN_ERR "%s: 0x%p", s, t->addr);
> + printk(KERN_ERR "%s: ", s);
> + __print_symbol("%s", (unsigned long)t->addr);
> printk(" jiffies_ago=%lu cpu=%u pid=%d\n", jiffies - t->when, t->cpu, t->pid);
> }
hm, that was a nice outcome.
We practically always have to cast the value when calling kallsyms functions.
I guess that means we goofed the design, should have made it void*.
--
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>
next prev parent reply other threads:[~2007-04-11 3:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 19:19 [SLUB 1/5] Fix object counting Christoph Lameter
2007-04-10 19:19 ` [SLUB 2/5] Enable tracking of full slabs Christoph Lameter
2007-04-10 19:19 ` [SLUB 3/5] Validation of slabs (metadata and guard zones) Christoph Lameter
2007-04-10 20:31 ` Andrew Morton
2007-04-10 20:47 ` Dave Jones
2007-04-10 21:42 ` Andrew Morton
2007-04-10 21:10 ` Christoph Lameter
2007-04-10 21:13 ` Christoph Lameter
2007-04-10 21:14 ` Christoph Lameter
2007-04-10 21:15 ` Christoph Lameter
2007-04-10 21:21 ` Christoph Lameter
2007-04-10 21:40 ` Christoph Lameter
2007-04-10 22:49 ` Christoph Lameter
2007-04-10 23:43 ` Andrew Morton
2007-04-10 23:17 ` Christoph Lameter
2007-04-10 23:38 ` Christoph Lameter
2007-04-11 0:00 ` Christoph Lameter
2007-04-11 0:15 ` Christoph Lameter
2007-04-11 6:24 ` question on mmap sameer sameer
2007-04-13 17:59 ` Hugh Dickins
2007-04-11 2:24 ` [SLUB 3/5] Validation of slabs (metadata and guard zones) Christoph Lameter
2007-04-11 3:08 ` Andrew Morton [this message]
2007-04-10 19:19 ` [SLUB 4/5] Add ability to list alloc / free callers per slab Christoph Lameter
2007-04-10 19:19 ` [SLUB 5/5] Drop version number 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=20070410200824.d116bbfd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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