From: Flavio Baronti <f.baronti-ngIpsMLAhaq41k5uCYKmRQ@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Leak in rdma_get_cm_event on pthread_cancel?
Date: Fri, 13 Jan 2012 17:55:02 +0100 [thread overview]
Message-ID: <4F1061E6.70901@list-group.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237325676E37-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Il 1/13/2012 17:43 PM, Hefty, Sean ha scritto:
>> When I want to stop the thread reading rdma events, I kill it with a
>> pthread_cancel(), since it is blocked in a
>> rdma_get_cm_event(). This causes a leak of the evt variable in the
>> rdma_get_cm_event() function. Not a big deal, of
>> course, but a couple of pthread_cleanup_push(free, evt) and
>> pthread_cleanup_pop() should solve it.
>
> What version of the librdmacm are you using?
I'm using 1.0.13; I checked in 1.0.15 too, and the code appears to have the same structure.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-13 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 11:46 Leak in rdma_get_cm_event on pthread_cancel? Flavio Baronti
[not found] ` <4F101978.6010608-ngIpsMLAhaq41k5uCYKmRQ@public.gmane.org>
2012-01-13 16:43 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237325676E37-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-01-13 16:55 ` Flavio Baronti [this message]
2012-01-13 17:59 ` Jason Gunthorpe
[not found] ` <20120113175925.GE6798-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-01-16 8:46 ` Flavio Baronti
[not found] ` <4F13E3ED.3010708-ngIpsMLAhaq41k5uCYKmRQ@public.gmane.org>
2012-01-16 22:15 ` Or Gerlitz
[not found] ` <CAJZOPZ+ik7DdXJHbEyr-PKyOQ3yEoWa6H=rhEe4cwc__61DUrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-16 22:35 ` Jason Gunthorpe
[not found] ` <20120116223541.GA2892-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-01-17 8:52 ` Flavio Baronti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1061E6.70901@list-group.com \
--to=f.baronti-ngipsmlahaq41k5ucykmrq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.