linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: colin wen <colinw21@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: sctp send and recv
Date: Mon, 21 Sep 2009 22:00:56 +0000	[thread overview]
Message-ID: <a87dbce20909211500webd96d9lef3f64deb11fbbbd@mail.gmail.com> (raw)
In-Reply-To: <a87dbce20909171629h274f02b5h28731245c0cb5ed7@mail.gmail.com>

On Mon, Sep 21, 2009 at 11:24 AM, Vlad Yasevich
<vladislav.yasevich@hp.com> wrote:
> colin wen wrote:
>> On Mon, Sep 21, 2009 at 6:45 AM, Vlad Yasevich
>> <vladislav.yasevich@hp.com> wrote:
>>> colin wen wrote:
>>>> I wrote a simple sctp server and client to test sctp in linux.
>>>> after client call connect, server accept return a socket,
>>>> but after client call send(fd, "hello", 5, 0) server's recv call
>>>> does not return, server's recv return after client close and
>>>> re-connect to server.
>>>> I wonder if someone could tell me what's the problem.
>>>> Thanks,
>>>
>>> What kernel version are you using?
>>>
>>> Can you post the source to your client and server?
>>>
>>> -vlad
>>>
>> I am using 2.6.28-13-generic (debian-5.0) and also
>> tested the kernel 2.6.31 downloaded from kernel.org.
>> Please find the following test code.
>
> Ok.  Just ran your server on a 2.6.31 kernel and it works perfectly fine.
> I tried running on the same system as well as 2 different ones.
>
> -vlad
>
Yes, I found the current code is working fine too.
I had tested by using printf("%s", buf);  which has no line break,
so did not output to my console, and I thought the recv call did not return.
sorry about that.
Thanks,
Colin

      parent reply	other threads:[~2009-09-21 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 23:29 sctp send and recv colin wen
2009-09-21 13:45 ` Vlad Yasevich
2009-09-21 16:40 ` colin wen
2009-09-21 18:24 ` Vlad Yasevich
2009-09-21 22:00 ` colin wen [this message]

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=a87dbce20909211500webd96d9lef3f64deb11fbbbd@mail.gmail.com \
    --to=colinw21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).