From: linux@horizon.com
To: linux@horizon.com, romieu@fr.zoreil.com
Cc: akpm@linux-foundation.org, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] drivers/net/ipg.c: Fix skbuff leak
Date: 8 Jan 2008 19:38:40 -0500 [thread overview]
Message-ID: <20080109003840.22917.qmail@science.horizon.com> (raw)
In-Reply-To: <20080108213640.GC4450@electric-eye.fr.zoreil.com>
> Can you try the patch below ?
Testing now... (I presume you noticed the one-character typo in my
earlier patch. That should be "mc = mc->next", not "mv = mc->next".)
That doesn't seem to do it. Not entirely, at least. After downloading
and partially re-uploading an 800M file, slabtop reports:
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
341576 341574 99% 0.50K 42697 8 170788K kmalloc-512
342006 341953 99% 0.19K 16286 21 65144K kmalloc-192
30592 30575 99% 2.00K 7648 4 61184K kmalloc-2048
30213 30193 99% 0.44K 3357 9 13428K skbuff_fclone_cache
7650 7643 99% 0.08K 150 51 600K sysfs_dir_cache
4000 3938 98% 0.12K 125 32 500K kmalloc-128
258 258 100% 1.15K 43 6 344K raid5-md5
232 221 95% 1.00K 58 4 232K kmalloc-1024
3136 3110 99% 0.06K 49 64 196K kmalloc-64
264 80 30% 0.68K 24 11 192K ext3_inode_cache
The "kmalloc-2048" was down in the noise before the upload started.
This is in single-user mode, after sync and echo 3 > /proc/sys/vm/drop_caches.
I'll have to try this after this evening's social plans, but I'm thinking
of implementing more rapid bug detection: explicitly zero the sp->TxBuff
slot when the skb is freed, and check that it is zero before putting
anything else in there. (And likewise for RxBuff.)
That way, I don't have to use up a noticeable amount of memory to see
the bug and reboot to clear up the damage each test cycle.
next prev parent reply other threads:[~2008-01-09 0:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 2:06 2.6.23-rc8 network problem. Mem leak? ip1000a? linux
2007-09-28 9:20 ` Andrew Morton
2007-09-30 7:59 ` linux
2007-09-30 9:23 ` Andrew Morton
2007-09-30 11:40 ` linux
2008-01-08 6:52 ` linux
2008-01-08 7:07 ` David Miller
2008-01-08 7:14 ` David Miller
2008-01-08 7:51 ` Francois Romieu
2008-01-08 12:28 ` [PATCH 1/3] drivers/net/ipg.c: Fix skbuff leak linux
2008-01-08 13:19 ` linux
2008-01-08 21:36 ` Francois Romieu
2008-01-08 23:00 ` David Miller
2008-01-08 23:28 ` Francois Romieu
2008-01-09 0:38 ` linux [this message]
2008-01-09 8:39 ` David Miller
2008-01-09 23:34 ` Francois Romieu
2008-01-09 23:56 ` David Miller
2008-01-09 23:30 ` Francois Romieu
2008-01-10 7:28 ` ipg.c bugs linux
-- strict thread matches above, loose matches on Subject: below --
2008-01-14 23:15 [PATCH 1/3] drivers/net/ipg.c: Fix skbuff leak Francois Romieu
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=20080109003840.22917.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).