All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: linux-sctp@vger.kernel.org
Subject: Re: undetected closed apps
Date: Thu, 19 Dec 2013 14:26:26 +0000	[thread overview]
Message-ID: <52B30212.5000607@mojatatu.com> (raw)
In-Reply-To: <52AC7375.6010505@mojatatu.com>

On 12/18/13 12:58, Vlad Yasevich wrote:
> On 12/18/2013 07:30 AM, Jamal Hadi Salim wrote:

> could you post an output for /proc/net/sctp/assocs for the association
> in this bad state?

It's not eye candy (lines wrap around). But here's one i just
reproduced with client/server on same machine via lo. It requires
a few tries to make sure we have send failed for this to happen.

----
SSOC     SOCK   STY SST ST HBKT ASSOC-ID TX_QUEUE RX_QUEUE UID INODE 
LPORT RPORT LADDRS <-> RADDRS HBINT INS OUTS MAXRT T1X T2X RTXC wmema 
wmemq sndbuf rcvbuf
        0        0 2   7   4  29808   11        0        0       0     0 
50902 30330  127.0.0.1 10.0.0.195 192.168.122.1 <-> *127.0.0.1      7500 
    10    10   10    0    0        0        1        0   212992   212992
        0        0 2   1   3  31695   12        0        0    1000 55928 
30330 50902  127.0.0.1 <-> *127.0.0.1 10.0.0.195 192.168.122.1      1500 
    10    10   10    0    0        0        1        0   212992   212992
---------

Server is at port 30330.

Actually i take back what i said earlier: When i write to this app, 
after it disconnects, i do see the socket queues grow for a short
period and then get drained to zero. I dont know where those messages
go. I monitor this by having the watch utility polling every second.

cheers,
jamal

  parent reply	other threads:[~2013-12-19 14:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 15:04 undetected closed apps Jamal Hadi Salim
2013-12-14 15:16 ` Jamal Hadi Salim
2013-12-14 15:27 ` Jamal Hadi Salim
2013-12-14 17:06 ` Michael Tuexen
2013-12-14 17:21 ` Jamal Hadi Salim
2013-12-14 17:23 ` Michael Tuexen
2013-12-14 17:36 ` Jamal Hadi Salim
2013-12-14 18:35 ` Jamal Hadi Salim
2013-12-14 18:47 ` Michael Tuexen
2013-12-14 19:09 ` Jamal Hadi Salim
2013-12-14 19:27 ` Jamal Hadi Salim
2013-12-14 20:06 ` Michael Tuexen
2013-12-15 15:21 ` Jamal Hadi Salim
2013-12-15 15:32 ` Michael Tuexen
2013-12-15 19:08 ` Jamal Hadi Salim
2013-12-16 15:19 ` Vlad Yasevich
2013-12-17 13:49 ` Jamal Hadi Salim
2013-12-17 15:11 ` Vlad Yasevich
2013-12-18 12:30 ` Jamal Hadi Salim
2013-12-18 17:58 ` Vlad Yasevich
2013-12-19 14:26 ` Jamal Hadi Salim [this message]
2013-12-19 17:24 ` Vlad Yasevich
2013-12-19 18:16 ` Vlad Yasevich
2013-12-20 12:23 ` Jamal Hadi Salim
2013-12-20 12:29 ` Jamal Hadi Salim
2013-12-20 17:00 ` Jamal Hadi Salim
2013-12-20 18:44 ` Jamal Hadi Salim

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=52B30212.5000607@mojatatu.com \
    --to=jhs@mojatatu.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.