PERFORCE change 105930 for review
John Baldwin
jhb at freebsd.org
Mon Sep 11 12:28:50 PDT 2006
On Monday 11 September 2006 14:51, Intron is my alias on the Internet wrote:
> Alexander Leidinger wrote:
>
> > Quoting John Baldwin <jhb at freebsd.org> (Mon, 11 Sep 2006 11:45:52 -0400):
> >
> >> On Sunday 10 September 2006 05:56, Alexander Leidinger wrote:
> >> > PROBLEMS:
> >> >
> >> > 1. Why does uma_zdestroy(9) print message like:
> >> >
> >> > Freed UMA keg was not empty (100 items). Lost 2 pages of
memory.
> >> >
> >> > Does it represent any problems?
> >>
> >> It means a memory leak.
> >
> > Because this is verbatim from the submitter and I don't know if he is
> > subscribed to perforce@, we should tell him about it... CCed. :-)
> >
> > Bye,
> > Alexander.
> >
>
> But I have ensure that calling to uma_zalloc() and calling to uma_zfree()
> appear strictly in pair in my code. Even the simplest testing program
> can still lead to this kind of warning message (uma_zfree() is just next
> to uma_zalloc()):
>
> uma_zalloc(...);
> uma_zfree(...);
I've only gotten this message when I've leaked memory in a zone. Do you have
an example self-contained kernel module that produces this?
--
John Baldwin
More information about the freebsd-hackers
mailing list