martin rogers wrote: > Corey Minyard wrote: > >> I don't know of any leak. Those things are counted and checked at >> module unload time. If you unload the ipmi_msghandler module, it should >> give you some idea if there's a leak. >> >> -Corey >> >> > No such luck -it prints nothing. > Lots of memory free after unloading though...
Maybe you are sending lots of messages and not receiving the responses and not closing the fd? Maybe killing a process frees the memory? There are no limits on the receive queue, but the queues will be cleaned up when you close fds. > > I'm not worried about ipmi_msghandler freeing pointers, passed to it by > ipmi_smi_msg_received(), when it's unloaded; I'm wondering what frees > this > memory during normal opreation. > > Where do msgs go that are passed in by ipmi_smi_msg_received() ? The upper layer handling should free the message. For instance, in ipmi_devintf (the user interface), the receive handler throws it into a queue and ioctl that reads the message will pull it from the queue free it (look for ipmi_free_recv_msg). -Corey > > Martin Rogers > > >> martin rogers wrote: >> >> >> >>> All, >>> >>> I have a kernel module that is calling into OpenIPMI, and memory is >>> being consumed (kmalloc'd) without being freed. >>> >>> I'm wondering what API, if any, might be involved in freeing the memory >>> being allocated. >>> >>> Without going into too much detail, we do: >>> >>> >>> struct ipmi_smi_msg smiMsg = ipmi_alloc_smi_msg(); >>> >>> .. fill in some stuff in smiMsg... >>> >>> ipmi_smi_msg_received(smi_intf, smiMsg); >>> >>> where smi_intf was gotten from ipmi_register_smi(...). >>> >>> >>> The only user space programs we're running are hpiel/hpigetevents, and >>> these >>> don't seem to free the memory allocated by ipmi_alloc_smi_msg(). >>> >>> Is there a userspace API that consumes the memory kmalloc'd by >>> ipmi_alloc_smi_msg/ipmi_smi_msg_received ? >>> >>> I don't know what ipmi_smi_msg_received does, so I'm lost.. >>> >>> Thanks in advance for any help or pointers... >>> >>> Using OpenIpmi 1.3.18, kernel 2.6.10. >>> >>> Martin Rogers >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by xPML, a groundbreaking scripting >>> language >>> that extends applications into web and mobile media. Attend the live >>> webcast >>> and join the prime developer group breaking into this new coding >>> territory! >>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>> >>> _______________________________________________ >>> Openipmi-developer mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/openipmi-developer >>> >> >> >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Openipmi-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openipmi-developer ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
