From: Andrew Morton <akpm@osdl.org>
To: adrian@smop.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-mm1 leaks in dvb playback
Date: Mon, 27 Mar 2006 17:23:56 -0800 [thread overview]
Message-ID: <20060327172356.7d4923d2.akpm@osdl.org> (raw)
In-Reply-To: <20060326211514.GA19287@wyvern.smop.co.uk>
Adrian Bridgett <adrian@smop.co.uk> wrote:
>
> I've had this problem for a little while (probably since 2.6.14/15
> era) but I've only recently spent some time to figure out what's been
> going wrong.
>
> There is a patch in the -mm series which causes leaks in both
> sock_inode_cache and dentry_cache for me during DVB playback (thanks
> to slabtop).
>
> 2.6.16 is fine (no leakage), 2.6.16-mm1 has this problem (~ 2MB/s in
> each cache).
Do you mean that the problem has been present in -mm kernels since the
2.6.14/15 timeframe, and not in mainline?
> I'm using dvbstream and sending the output to /dev/null, dvb modules
> loaded are dvb_usb_vp7045, dvb_usb, dvb_core, dvb_pll. It's an EHCI USB
> device running on a Dell D600 latitude.
>
> turning on some debugging and looking at /proc/slab_allocators and
> /proc/page_owners shows that the most prevalent page owners are:
>
> (5363 out of 5631)
> Page allocated via order 0, mask 0xd0
> [0xc0161079] poison_obj+41
> [0xc0162355] cache_alloc_refill+981
> [0xc0161889] cache_alloc_debugcheck_after+169
> [0xc01d5169] vsnprintf+857
> [0xc0247eec] lock_sock+204
> [0xc0244999] sock_alloc_inode+25
> [0xc0161f73] kmem_cache_alloc+131
> [0xc027a4b4] inet_csk_accept+436
>
> (1989 out of 2734)
> Page allocated via order 0, mask 0xd0
> [0xc0162355] cache_alloc_refill+981
> [0xc0161079] poison_obj+41
> [0xc0161079] poison_obj+41
> [0xc01d5169] vsnprintf+857
> [0xc0182341] d_alloc+33
> [0xc0161f73] kmem_cache_alloc+131
> [0xc0182341] d_alloc+33
> [0xc02461e0] sock_attach_fd+96
>
Strange. Are you sure that they really leak? Doing
echo 3 > /proc/sys/vm/drop_caches
doesn't make them go away?
next prev parent reply other threads:[~2006-03-28 1:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:15 2.6.16-mm1 leaks in dvb playback Adrian Bridgett
2006-03-28 1:23 ` Andrew Morton [this message]
2006-03-28 7:02 ` adrian
2006-03-28 7:16 ` Andrew Morton
2006-03-29 23:37 ` adrian
2006-03-30 0:06 ` Andrew Morton
2006-03-30 0:45 ` Adrian Bridgett
2006-03-30 22:58 ` 2.6.16-mm1 leaks in dvb playback (found) Adrian Bridgett
2006-03-30 23:11 ` Adrian Bridgett
2006-03-30 23:28 ` David S. Miller
2006-03-31 1:22 ` Andi Kleen
2006-03-31 7:28 ` Adrian Bridgett
2006-03-31 7:48 ` David S. Miller
2006-03-31 9:54 ` Adrian Bridgett
2006-03-31 10:07 ` David S. Miller
2006-03-31 18:47 ` Adrian Bridgett
2006-03-28 7:23 ` 2.6.16-mm1 leaks in dvb playback adrian
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=20060327172356.7d4923d2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adrian@smop.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.