Kernel memory leak?

[Poul-Henning Kamp]

In message <55218.1050439220 at wcom.com>, "Ian Freislich" writes:

>Running this program, resulted in my server panicing after about
>15 minutes (15000 iterations).  Watching top, the 'wired' memory
>slowly increases increases until the system panics with the message
>below.  It's very repeatable, so I can get a more detailed backtrace
>if required.

That looks like a memory leak in my department, I'll fix it before 5.1.

Poul-Henning

># There must be a better way to do this

I suggest instead you search for valid superblocks, they have a 
well-defined magic word you could look for.

I even belive I have seen reports of a tool that does it automatically,
but have no references at hand.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.