[ofa-general] ib_rdma_bw - memory leaks?

[Sumit Panchasara]

Yes, rdma_cma_fini() calls the ucma_cleanup() on lib unload (usually after
main() is returned) as it is declared with "__attribute__((destructor))".
I observed its address written inside .dtors section in objdump.

As mentioned in my previous email, there are other 3 places of memory leaks,
should I proceed and fix them up in rdma_bw.c file?

Thanks,
Sumit


-----Original Message-----
From: Sean Hefty [mailto:sean.hefty at intel.com] 
Sent: Wednesday, July 01, 2009 9:36 PM
To: 'Sumit Panchasara'; ewg at lists.openfabrics.org;
general at lists.openfabrics.org
Subject: RE: [ofa-general] ib_rdma_bw - memory leaks?

>3. rdma_create_event_channel() calls ucma_init() but
>rdma_destroy_event_channel() does not call ucma_cleanup(), this results
into
>memory leak at provider's library since it does not call ibv_close_device()
>and thus unable to do *->free_context().

This is the correct behavior.  ucma_init() is called from several routines
to
ensure that the library performs proper initialization.  Once initialized,
it
remains initialized until the library is no longer used.  The cleanup is
done in
rdma_cma_fini().

- Sean




Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com

-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________