From: Daniel Borkmann <dborkman@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: [PATCH net-next 0/4] Some SCTP cleanups/improvements
Date: Thu, 13 Jun 2013 18:04:19 +0200 [thread overview]
Message-ID: <1371139463-12512-1-git-send-email-dborkman@redhat.com> (raw)
v1 -> v2:
- Apply Neil's feedback, I'll send out the first patch at a later
point in time though, have not included it in this set
- Add two other patches that appear to be useful from the last
couple of days debugging SCTP code
Daniel Borkmann (4):
net: sctp: throw BUG if primary_path in sctp_seq_dump_local_addrs is NULL
net: sctp: sctp_sf_do_prm_asoc: do SCTP_CMD_INIT_CHOOSE_TRANSPORT first
net: sctp: minor: remove variable in sctp_init_sock
net: sctp: sctp_association_init: put refs in reverse order on error
net/sctp/associola.c | 7 +++----
net/sctp/proc.c | 15 ++++++++++++---
net/sctp/sm_statefuns.c | 8 ++++----
net/sctp/socket.c | 6 ++----
4 files changed, 21 insertions(+), 15 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-06-13 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 16:04 Daniel Borkmann [this message]
2013-06-13 16:04 ` [PATCH net-next 1/4] net: sctp: sctp_seq_dump_local_addrs: throw BUG if primary_path is NULL Daniel Borkmann
2013-06-14 14:33 ` Vlad Yasevich
2013-06-14 14:51 ` Daniel Borkmann
2013-06-14 15:04 ` Vlad Yasevich
2013-06-13 16:04 ` [PATCH net-next 2/4] net: sctp: sctp_sf_do_prm_asoc: do SCTP_CMD_INIT_CHOOSE_TRANSPORT first Daniel Borkmann
2013-06-13 16:04 ` [PATCH net-next 3/4] net: sctp: minor: remove variable in sctp_init_sock Daniel Borkmann
2013-06-13 16:04 ` [PATCH net-next 4/4] net: sctp: sctp_association_init: put refs in reverse order Daniel Borkmann
2013-06-14 0:45 ` [PATCH net-next 0/4] Some SCTP cleanups/improvements David Miller
2013-06-14 14:07 ` 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=1371139463-12512-1-git-send-email-dborkman@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@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).