From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "honli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<honli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"jgg-uk2M96/98Pc@public.gmane.org"
<jgg-uk2M96/98Pc@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-core] srp_daemon: Install signal handler for ibsrpdm
Date: Fri, 15 Dec 2017 17:50:54 +0000 [thread overview]
Message-ID: <1513360253.2571.23.camel@wdc.com> (raw)
In-Reply-To: <20171215172800.GA12434-uk2M96/98Pc@public.gmane.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1045 bytes --]
On Fri, 2017-12-15 at 10:28 -0700, Jason Gunthorpe wrote:
> Though overall, there is really no reason to even cleanup the threads,
> just call exit?
Memory leak detectors like the one in Valgrind only produce meaningful results
if threads are stopped cleanly before exit() is called.
> @@ -1887,7 +1888,9 @@ static void free_res(struct resources *res)
> modify_qp_to_err(res->ud_res->qp);
>
> if (res->reconnect_thread) {
> - pthread_kill(res->reconnect_thread, SIGINT);
> + uint64_t val = 1;
> +
> + write(res->sync_res->stop_event_fd, &val, sizeof(val));
> pthread_join(res->reconnect_thread, &status);
This patch does not remove all pthread_kill() calls. There are two other such
calls:
$ git grep -nHw pthread_kill
srp_daemon/srp_daemon.c:1897: pthread_kill(res->async_ev_thread, SIGINT);
srp_daemon/srp_daemon.c:1901: pthread_kill(res->trap_thread, SIGINT);
Bart.N§²æìr¸yúèØb²X¬¶Ç§vØ^)Þº{.nÇ+·¥{±Ù{ayº\x1dÊÚë,j\a¢f£¢·h»öì\x17/oSc¾Ú³9uÀ¦æåÈ&jw¨®\x03(éÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þàþf£¢·h§~m
next prev parent reply other threads:[~2017-12-15 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 11:02 [PATCH rdma-core] srp_daemon: Install signal handler for ibsrpdm Honggang LI
[not found] ` <20171214110241.4701-1-honli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-12-14 14:59 ` Bart Van Assche
[not found] ` <1513263572.2986.2.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-15 1:36 ` Honggang LI
[not found] ` <20171215013628.GA743-Y5OA6DF/u0nid9cnFhDO8BcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2017-12-15 17:28 ` Jason Gunthorpe
[not found] ` <20171215172800.GA12434-uk2M96/98Pc@public.gmane.org>
2017-12-15 17:50 ` Bart Van Assche [this message]
[not found] ` <1513360253.2571.23.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-15 17:59 ` Jason Gunthorpe
2017-12-19 12:20 ` Honggang LI
[not found] ` <20171219122050.GA19682-Y5OA6DF/u0nid9cnFhDO8BcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2017-12-19 16:57 ` Bart Van Assche
[not found] ` <1513702653.2535.3.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-19 19:12 ` Honggang LI
2017-12-19 21:13 ` Jason Gunthorpe
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=1513360253.2571.23.camel@wdc.com \
--to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
--cc=honli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox