All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Kumar <svashok79@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: How to restrict SCTP abort during a process crash
Date: Tue, 12 Dec 2017 16:51:41 +0000	[thread overview]
Message-ID: <CAOTBYLYCFVt0hHf5_pJQCEPsh9vSNXR3V7b0SaVycJ4-KZja0w@mail.gmail.com> (raw)

Hi,



We are using LKSCTP in our LTE product (HeNBGW). We have
high-availability support also in our product. In case of any failure
on active VM, standby VM will take over active role and all the SCTP
associations will be moved to that new active VM. The associations
should be moved transparent to the peers (a kind of SCTP reset before
SCTP heartbeat expires on the peer nodes).



But the problem that we face is that when a process crashes on active
VM, the LKSCTP stack immediately sends SCTP abort to the peers for all
associations before the system goes down completely. This creates
confusion with the peers. Is there any way to avoid sending SCTP abort
message in this scenario? If yes, please let us know how to do the
same? If it needs LKSCTP kernel code change, please give pointers on
what and where to change.



P.S: We tried to block the abort messages by dynamically using
IPtables through signal handler (for signal 11 and 6). But this did
not work.



A quick response will be highly appreciated.



Thanks,

Ashok

             reply	other threads:[~2017-12-12 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 16:51 Ashok Kumar [this message]
2017-12-12 18:32 ` How to restrict SCTP abort during a process crash Neil Horman
2017-12-12 19:38 ` Marcelo Ricardo Leitner
2017-12-13  4:50 ` Ashok Kumar
2017-12-13  6:58 ` Xin Long
2017-12-13 12:22 ` Neil Horman
2017-12-14  6:42 ` Ashok Kumar
2017-12-14  9:22 ` Xin Long
2017-12-14 10:40 ` Neil Horman

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=CAOTBYLYCFVt0hHf5_pJQCEPsh9vSNXR3V7b0SaVycJ4-KZja0w@mail.gmail.com \
    --to=svashok79@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.