From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
Xin Long <lucien.xin@gmail.com>
Subject: Re: [PATCH net-next v2 3/8] sctp: move the flush of ctrl chunks into its own function
Date: Sun, 13 May 2018 21:21:09 -0300 [thread overview]
Message-ID: <20180514002109.GZ5105@localhost.localdomain> (raw)
In-Reply-To: <629f02a784ff90761adee451a870c7548069287d.1526142784.git.marcelo.leitner@gmail.com>
On Sat, May 12, 2018 at 07:21:01PM -0300, Marcelo Ricardo Leitner wrote:
> Named sctp_outq_flush_ctrl and, with that, keep the contexts contained.
Trinity triggered a panic on this patch. I'm debugging it.
next prev parent reply other threads:[~2018-05-14 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 22:20 [PATCH net-next v2 0/8] sctp: refactor sctp_outq_flush Marcelo Ricardo Leitner
2018-05-12 22:20 ` [PATCH net-next v2 1/8] sctp: add sctp_packet_singleton Marcelo Ricardo Leitner
2018-05-12 22:20 ` [PATCH net-next v2 2/8] sctp: factor out sctp_outq_select_transport Marcelo Ricardo Leitner
2018-05-12 22:21 ` [PATCH net-next v2 3/8] sctp: move the flush of ctrl chunks into its own function Marcelo Ricardo Leitner
2018-05-14 0:21 ` Marcelo Ricardo Leitner [this message]
2018-05-12 22:21 ` [PATCH net-next v2 4/8] sctp: move outq data rtx code out of sctp_outq_flush Marcelo Ricardo Leitner
2018-05-12 22:21 ` [PATCH net-next v2 5/8] sctp: move flushing of data chunks " Marcelo Ricardo Leitner
2018-05-12 22:21 ` [PATCH net-next v2 6/8] sctp: move transport flush code " Marcelo Ricardo Leitner
2018-05-12 22:21 ` [PATCH net-next v2 7/8] sctp: make use of gfp on retransmissions Marcelo Ricardo Leitner
2018-05-12 22:21 ` [PATCH net-next v2 8/8] sctp: rework switch cases in sctp_outq_flush_data Marcelo Ricardo Leitner
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=20180514002109.GZ5105@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--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).