All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: undetected closed apps
Date: Tue, 17 Dec 2013 15:11:32 +0000	[thread overview]
Message-ID: <52B069A4.500@gmail.com> (raw)
In-Reply-To: <52AC7375.6010505@mojatatu.com>

On 12/17/2013 08:49 AM, Jamal Hadi Salim wrote:
> On 12/16/13 10:19, Vlad Yasevich wrote:
>> On 12/14/2013 10:04 AM, Jamal Hadi Salim wrote:
> 
>> Hi Jamal
>>
>> The only thing I can think off that may be causing this is the
>> rcu-fication of the transport list in the associations.
>>
>> You might be able to test by reverting:
>>    771085d6bf3c52de29fc213e5bad07a82e57c23e
>>    8c98653f05534acd1cb07ea4929702a3659177d1
>>    45122ca26ced7fae41049326a3797a73f961db2e
> 
> 
> Thanks Vlad. I will try newer kernels and revert these changes
> incrementally and see if there's improvement.
> 
> BTW: What tools are useful to monitor sctp behavior?
> For this case I have been watching activity using
> /proc/net/sctp/assocs, strace and tcpdump.

That's about it.  You can also use stap.  It's on the project
todo list to provide some good stap scripts.

The other thing that is useful for debugging things like this is
the object counting in SCTP (CONFIG_SCTP_DBG_OBJCNT), but it's a
kernel config option so not sure how easily you'd be able to use
it.

> 
> cheers,
> jamal
> 
> PS: I currently have no choice on what kernels already deployed
> that need the software feature but can make recommendations
> for future upgrades. It would be good to narrow it down.

The initial commit 45122ca26ced7fae41049326a3797a73f961db2e was
added to 3.8.  In 3.9 we fixed a bug where the association closures
were being delayed too long and were preventing socket rebinding
(commit 8c98653f05534acd1cb07ea4929702a3659177d1).

  parent reply	other threads:[~2013-12-17 15:11 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 [this message]
2013-12-18 12:30 ` Jamal Hadi Salim
2013-12-18 17:58 ` Vlad Yasevich
2013-12-19 14:26 ` Jamal Hadi Salim
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=52B069A4.500@gmail.com \
    --to=vyasevich@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.