From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 rdma-core] srp_daemon: Remove duplicate sync_res shutdown
Date: Tue, 19 Dec 2017 14:51:02 -0700 [thread overview]
Message-ID: <20171219215102.GA28841@ziepe.ca> (raw)
The very first thing free_res does is the same lock/signal/unlock
sequence, so there is no reason to open code it before calling
free_res.
res->sync_res always exists at this point so remove the assert too.
Signed-off-by: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
---
srp_daemon/srp_daemon.c | 6 ------
1 file changed, 6 deletions(-)
v3:
- Delete stray edit
Bart, Yes, must have been a stray editor edit, I did not even look at v2 in
the mailer before sending it, since the one line change was so simple :(
This one compiles.
diff --git a/srp_daemon/srp_daemon.c b/srp_daemon/srp_daemon.c
index cec36db2e0f12e..5995e6a6173046 100644
--- a/srp_daemon/srp_daemon.c
+++ b/srp_daemon/srp_daemon.c
@@ -2073,12 +2073,6 @@ static int ibsrpdm(int argc, char *argv[])
if (ret)
pr_err("Querying SRP targets failed\n");
- assert(res->sync_res);
- pthread_mutex_lock(&res->sync_res->retry_mutex);
- res->sync_res->stop_threads = 1;
- pthread_cond_signal(&res->sync_res->retry_cond);
- pthread_mutex_unlock(&res->sync_res->retry_mutex);
-
free_res(res);
umad_done:
umad_done();
--
2.15.1
--
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 reply other threads:[~2017-12-19 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 21:51 Jason Gunthorpe [this message]
[not found] ` <20171219215102.GA28841-uk2M96/98Pc@public.gmane.org>
2017-12-19 22:18 ` [PATCH v3 rdma-core] srp_daemon: Remove duplicate sync_res shutdown Bart Van Assche
2017-12-20 7:20 ` Honggang LI
2017-12-25 10:31 ` Leon Romanovsky
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=20171219215102.GA28841@ziepe.ca \
--to=jgg-vpraknaxozvwk0htik3j/w@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