From: Parag Warudkar <kernel-stuff@comcast.net>
To: Andrew Morton <akpm@osdl.org>
Cc: noel@zhtwn.com, torvalds@osdl.org, kas@fi.muni.cz, axboe@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]
Date: Thu, 17 Feb 2005 08:00:27 -0500 [thread overview]
Message-ID: <200502170800.28012.kernel-stuff@comcast.net> (raw)
In-Reply-To: <20050216155255.0ffab555.akpm@osdl.org>
On Wednesday 16 February 2005 06:52 pm, Andrew Morton wrote:
> So it's probably an ndiswrapper bug?
Andrew,
It looks like it is a kernel bug triggered by NdisWrapper. Without
NdisWrapper, and with just 8139too plus some light network activity the
size-64 grew from ~ 1100 to 4500 overnight. Is this normal? I will keep it
running to see where it goes.
A question - is it safe to assume it is a kmalloc based leak? (I am thinking
of tracking it down by using kprobes to insert a probe into __kmalloc and
record the stack to see what is causing so many allocations.)
Thanks
Parag
next prev parent reply other threads:[~2005-02-17 13:00 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 16:19 Memory leak in 2.6.11-rc1? Jan Kasprzak
2005-01-22 2:23 ` Alexander Nyberg
2005-01-23 9:11 ` Jens Axboe
2005-01-23 9:19 ` Andrew Morton
2005-01-23 9:56 ` Jens Axboe
2005-01-23 10:32 ` Andrew Morton
2005-01-23 20:03 ` Russell King
2005-01-24 11:48 ` Russell King
2005-01-25 19:32 ` Russell King
2005-01-27 8:28 ` Russell King
2005-01-27 8:47 ` Andrew Morton
2005-01-27 10:19 ` Alessandro Suardi
2005-01-27 12:17 ` Martin Josefsson
2005-01-27 12:56 ` Robert Olsson
2005-01-27 13:03 ` Robert Olsson
2005-01-27 16:49 ` Russell King
2005-01-27 18:37 ` Phil Oester
2005-01-27 19:25 ` Russell King
2005-01-27 20:40 ` Phil Oester
2005-01-28 9:32 ` Russell King
2005-01-27 20:33 ` David S. Miller
2005-01-28 0:17 ` Russell King
2005-01-28 0:34 ` David S. Miller
2005-01-28 8:58 ` Russell King
2005-01-30 13:23 ` Russell King
2005-01-30 15:34 ` Russell King
2005-01-30 16:57 ` Phil Oester
2005-01-30 17:23 ` Patrick McHardy
2005-01-30 17:26 ` Patrick McHardy
2005-01-30 17:58 ` Patrick McHardy
2005-01-30 18:45 ` Russell King
2005-01-31 2:48 ` David S. Miller
2005-01-31 4:11 ` Herbert Xu
2005-01-31 4:45 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-31 5:00 ` Patrick McHardy
2005-01-31 5:11 ` David S. Miller
2005-01-31 5:40 ` Herbert Xu
2005-01-31 5:16 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-31 5:42 ` Yasuyuki KOZAKAI
2005-01-30 18:01 ` Russell King
2005-01-30 18:19 ` Phil Oester
2005-01-28 1:41 ` Phil Oester
2005-01-24 0:56 ` Alexander Nyberg
2005-01-24 20:47 ` Jens Axboe
2005-01-24 20:56 ` Andrew Morton
2005-01-24 21:05 ` Jens Axboe
2005-01-24 22:35 ` Linus Torvalds
2005-01-25 15:53 ` OT " Paulo Marques
2005-01-26 8:01 ` Jens Axboe
2005-01-26 8:11 ` Andrew Morton
2005-01-26 8:40 ` Jens Axboe
2005-01-26 8:44 ` Andrew Morton
2005-01-26 8:47 ` Jens Axboe
2005-01-26 8:52 ` Jens Axboe
2005-01-26 9:00 ` William Lee Irwin III
2005-01-26 8:58 ` Andrew Morton
2005-01-26 9:03 ` Jens Axboe
2005-01-26 15:52 ` Parag Warudkar
2005-02-02 9:29 ` Lennert Van Alboom
2005-02-02 16:00 ` Linus Torvalds
2005-02-02 16:19 ` Lennert Van Alboom
2005-02-02 17:49 ` Dave Hansen
2005-02-02 18:27 ` Linus Torvalds
2005-02-02 19:07 ` Dave Hansen
2005-02-02 21:08 ` Linus Torvalds
2005-01-24 22:05 ` Andrew Morton
2005-02-07 11:00 ` Jan Kasprzak
2005-02-07 11:11 ` William Lee Irwin III
2005-02-07 15:38 ` Linus Torvalds
2005-02-07 15:52 ` Jan Kasprzak
2005-02-07 16:38 ` axboe
2005-02-07 17:35 ` Jan Kasprzak
2005-02-07 21:10 ` Jan Kasprzak
2005-02-08 2:47 ` Memory leak in 2.6.11-rc1? (also here) Noel Maddy
2005-02-16 4:00 ` -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?] Parag Warudkar
2005-02-16 5:12 ` Andrew Morton
2005-02-16 6:07 ` Parag Warudkar
2005-02-16 23:52 ` Andrew Morton
2005-02-17 13:00 ` Parag Warudkar [this message]
2005-02-17 18:18 ` Linus Torvalds
2005-02-18 1:38 ` Badari Pulavarty
2005-02-21 4:57 ` Parag Warudkar
2005-02-16 23:31 ` Parag Warudkar
2005-02-16 23:51 ` Andrew Morton
2005-02-17 1:19 ` Parag Warudkar
2005-02-17 3:48 ` Horst von Brand
2005-02-17 13:35 ` Parag Warudkar
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=200502170800.28012.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=kas@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=noel@zhtwn.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).