From: sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 2/2] rsocket: Update correct rsocket keepalive time
Date: Thu, 3 Jul 2014 15:08:44 -0700 [thread overview]
Message-ID: <1404425324-20201-2-git-send-email-sean.hefty@intel.com> (raw)
In-Reply-To: <1404425324-20201-1-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
From: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
When the keepalive time of an rsocket is updated, the
updated information is forwarded to the keepalive service
thread. However, the thread updates the time for the
wrong service as shown:
tcp_svc_timeouts[svc->cnt] = rs_get_time() + msg.rs->keepalive_time;
The index into tcp_svc_timeouts should correspond to the
rsocket being updated, not the last one in the list.
Signed-off-by: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
---
src/rsocket.c | 37 ++++++++++++++++++++++++++-----------
1 files changed, 26 insertions(+), 11 deletions(-)
diff --git a/src/rsocket.c b/src/rsocket.c
index e9d12c7..b869d88 100644
--- a/src/rsocket.c
+++ b/src/rsocket.c
@@ -3941,19 +3941,28 @@ static int rs_svc_add_rs(struct rs_svc *svc, struct rsocket *rs)
return 0;
}
-static int rs_svc_rm_rs(struct rs_svc *svc, struct rsocket *rs)
+static int rs_svc_index(struct rs_svc *svc, struct rsocket *rs)
{
int i;
for (i = 1; i <= svc->cnt; i++) {
- if (svc->rss[i] == rs) {
- svc->rss[i] = svc->rss[svc->cnt];
- memcpy(svc->contexts + i * svc->context_size,
- svc->contexts + svc->cnt * svc->context_size,
- svc->context_size);
- svc->cnt--;
- return 0;
- }
+ if (svc->rss[i] == rs)
+ return i;
+ }
+ return -1;
+}
+
+static int rs_svc_rm_rs(struct rs_svc *svc, struct rsocket *rs)
+{
+ int i;
+
+ if ((i = rs_svc_index(svc, rs)) >= 0) {
+ svc->rss[i] = svc->rss[svc->cnt];
+ memcpy(svc->contexts + i * svc->context_size,
+ svc->contexts + svc->cnt * svc->context_size,
+ svc->context_size);
+ svc->cnt--;
+ return 0;
}
return EBADF;
}
@@ -4197,6 +4206,7 @@ static uint32_t rs_get_time(void)
static void tcp_svc_process_sock(struct rs_svc *svc)
{
struct rs_svc_msg msg;
+ int i;
read(svc->sock[1], &msg, sizeof msg);
switch (msg.cmd) {
@@ -4215,8 +4225,13 @@ static void tcp_svc_process_sock(struct rs_svc *svc)
msg.rs->opts &= ~RS_OPT_SVC_ACTIVE;
break;
case RS_SVC_MOD_KEEPALIVE:
- tcp_svc_timeouts[svc->cnt] = rs_get_time() + msg.rs->keepalive_time;
- msg.status = 0;
+ i = rs_svc_index(svc, msg.rs);
+ if (i >= 0) {
+ tcp_svc_timeouts[i] = rs_get_time() + msg.rs->keepalive_time;
+ msg.status = 0;
+ } else {
+ msg.status = EBADF;
+ }
break;
case RS_SVC_NOOP:
msg.status = 0;
--
1.7.3
--
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:[~2014-07-03 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 22:08 [PATCH 1/2] rsocket: Fix removing rsocket from service thread sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1404425324-20201-1-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-03 22:08 ` sean.hefty-ral2JQCrhuEAvxtiuMwx3w [this message]
[not found] ` <1404425324-20201-2-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-07 10:08 ` [PATCH 2/2] rsocket: Update correct rsocket keepalive time Hal Rosenstock
2014-07-07 10:08 ` [PATCH 1/2] rsocket: Fix removing rsocket from service thread Hal Rosenstock
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=1404425324-20201-2-git-send-email-sean.hefty@intel.com \
--to=sean.hefty-ral2jqcrhueavxtiumwx3w@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 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.