Re: 2.0.33 Memory leak (bad)

Kai Henningsen (xpost-complain@khms.westfalen.de)
10 Jan 1998 20:26:00 +0200


mikeg@weiden.de (Michael L. Galbraith) wrote on 10.01.98 in <Pine.LNX.3.95.980110094816.370A-100000@mikeg.weiden.de>:

> On 9 Jan 1998, Kai Henningsen wrote:

> > Did that. It needed one minow tweak: change all #define kfree(...) xx(...)
> > into #define kfree xx, otherwise the NCR 7/8xx driver won't compile (it
> > takes the address of kfree).
> >
>
> If I were you, I'd write a local kfree func so I didn't have to fiddle
> with the kfree wrapping. Also, casting kfree to void kfree(void *, int)
> isn't ok.. is it?

I'll have a look at that.

> > However, I can look at the results 'til my eyes fall out and still not see
> > the problem.
> >
> > Attached are outputs from free, ps -lax, and dosum, from a time where the
> > system seems to already have lost significant memory.
>
> I looked at the output, and it appears that someone is vmallocing like
> *mad*. You could try wrapping vmalloc to see who's doing that.

Will look at that, too.

> You aren't running an SMP kernel on a UP box are you?

Hmm ... it's possible, didn't touch that ... nope. Anyway, it sure
shouldn't leak like crazy :-)

MfG Kai