From: Karl Heiss <kheiss@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>
Subject: [PATCH net 0/2] sctp: Fix SCTP deadlock
Date: Thu, 24 Sep 2015 12:15:05 -0400 [thread overview]
Message-ID: <1443111307-16503-1-git-send-email-kheiss@gmail.com> (raw)
These patches fix a deadlock during accept() of an SCTP connection.
The first patch fixes whitespace issues.
The second patch actually fixes the deadlock race.
Karl Heiss (2):
sctp: Whitespace fix
sctp: Prevent soft lockup when sctp_accept() is called during a
timeout event
net/sctp/sm_sideeffect.c | 44 ++++++++++++++++++++++++--------------------
1 files changed, 24 insertions(+), 20 deletions(-)
next reply other threads:[~2015-09-24 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 16:15 Karl Heiss [this message]
2015-09-24 16:15 ` [PATCH net 1/2] sctp: Whitespace fix Karl Heiss
2015-09-24 16:15 ` [PATCH net 2/2] sctp: Prevent soft lockup when sctp_accept() is called during a timeout event Karl Heiss
2015-09-25 19:52 ` [PATCH net 0/2] sctp: Fix SCTP deadlock Marcelo Ricardo Leitner
2015-09-28 10:35 ` Neil Horman
2015-09-29 4:03 ` David Miller
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=1443111307-16503-1-git-send-email-kheiss@gmail.com \
--to=kheiss@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
/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).