From: Hangbin Liu <liuhangbin@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [lksctp-developers] [PATCH] sctp_status: server side should also receive msg_cnt times
Date: Wed, 30 Oct 2013 00:54:11 +0000 [thread overview]
Message-ID: <20131030005411.GC14331@localhost.localdomain> (raw)
In-Reply-To: <1382842583-890-1-git-send-email-liuhangbin@gmail.com>
On Sun, Oct 27, 2013 at 10:56:23AM +0800, Hangbin Liu wrote:
> As client side send msg_cnt times for each repeat. Server will exit too early
> if we only receive one time for each repeat and leave client keep sent, which
> makes client could not exit normally
>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
> src/apps/sctp_status.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/src/apps/sctp_status.c b/src/apps/sctp_status.c
> index 4e21af8..76f96e4 100644
> --- a/src/apps/sctp_status.c
> +++ b/src/apps/sctp_status.c
> @@ -547,6 +547,8 @@ int receive_r(int sk)
> } /* receive_r () */
>
> void server(int sk) {
> + int i;
> +
> if (max_msgsize > DEFAULT_MAX_WINDOW) {
> if (setsockopt(sk, IPPROTO_SCTP, SO_RCVBUF, &max_msgsize,
> sizeof(max_msgsize)) < 0) {
> @@ -555,7 +557,10 @@ void server(int sk) {
> }
> }
>
> - receive_r(sk);
> + for (i = 0; i < msg_cnt; i++) {
> + receive_r(sk);
> + DEBUG_PRINT(DEBUG_MIN, "count %d\n", i+1);
> + }
> } /* server() */
>
> void * build_msg(int len) {
> --
> 1.8.1.4
>
How about this patch?
--
Thanks & Best Regards
Hangbin Liu <liuhangbin@gmail.com>
next prev parent reply other threads:[~2013-10-30 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 2:56 [lksctp-developers] [PATCH] sctp_status: server side should also receive msg_cnt times Hangbin Liu
2013-10-30 0:54 ` Hangbin Liu [this message]
2013-10-30 8:10 ` Daniel Borkmann
2013-10-30 13:39 ` Daniel Borkmann
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=20131030005411.GC14331@localhost.localdomain \
--to=liuhangbin@gmail.com \
--cc=linux-sctp@vger.kernel.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.