Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]
From: Parag Warudkar (kernel-stuff_at_comcast.net)
Date: 02/21/05
- Previous message: Ian Kent: "Re: [autofs] automount does not close file descriptors at start"
- In reply to: Badari Pulavarty: "Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]"
- Next in thread: Andrew Morton: "Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Badari Pulavarty <pbadari@us.ibm.com> Date: Sun, 20 Feb 2005 23:57:40 -0500
On Thursday 17 February 2005 08:38 pm, Badari Pulavarty wrote:
> > 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.
[OT]
Didn't wanted to keep this hanging - It turned out to be a strange ndiswrapper
bug - It seems that the other OS in question allows the following without a
leak ;) -
ptr =Allocate(...);
ptr = Allocate(...);
:
repeat this zillion times without ever fearing that 'ptr' will leak..
I sent a fix to ndiswrapper-general mailing list on sourceforge if any one is
using ndiswrapper and having a similar problem.
Parag
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Ian Kent: "Re: [autofs] automount does not close file descriptors at start"
- In reply to: Badari Pulavarty: "Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]"
- Next in thread: Andrew Morton: "Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
