From: Pavel Emelianov <xemul@openvz.org>
To: akpm@osdl.org
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH -mm] Fix /proc/slab_allocators re seq_list_next() conversion
Date: Mon, 04 Jun 2007 16:42:42 +0400 [thread overview]
Message-ID: <466408C2.3000406@openvz.org> (raw)
In-Reply-To: <20070604122616.GA6155@localhost.sw.ru>
Alexey Dobriyan wrote:
> Wrong pointer was used as kmem_cache pointer.
>
> [Here /proc/slab_allocators appears as empty file, but it's just me, probably]
>
> Signed-off-by: Alexey Dobriyan <adobriyan@sw.ru>
Acked-by: Pavel Emelianov <xemul@openvz.org>
> ---
>
> mm/slab.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -4401,7 +4401,7 @@ static void show_symbol(struct seq_file *m, unsigned long address)
>
> static int leaks_show(struct seq_file *m, void *p)
> {
> - struct kmem_cache *cachep = p;
> + struct kmem_cache *cachep = list_entry(p, struct kmem_cache, next);
> struct slab *slabp;
> struct kmem_list3 *l3;
> const char *name;
>
>
prev parent reply other threads:[~2007-06-04 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:26 [PATCH -mm] Fix /proc/slab_allocators re seq_list_next() conversion Alexey Dobriyan
2007-06-04 12:42 ` Pavel Emelianov [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=466408C2.3000406@openvz.org \
--to=xemul@openvz.org \
--cc=adobriyan@sw.ru \
--cc=akpm@osdl.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.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