From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, davem@davemloft.net,
Vlad Yasevich <vyasevich@gmail.com>,
daniel@iogearbox.net
Subject: Re: [PATCHv2 net 0/6] sctp: fix the transmit err process
Date: Wed, 14 Sep 2016 14:16:05 -0300 [thread overview]
Message-ID: <20160914171605.GG17689@localhost.localdomain> (raw)
In-Reply-To: <cover.1473789537.git.lucien.xin@gmail.com>
On Wed, Sep 14, 2016 at 02:04:17AM +0800, Xin Long wrote:
> This patchset is to improve the transmit err process and also fix some
> issues.
>
> After this patchset, once the chunks are enqueued successfully, even
> if the chunks fail to send out, no matter because of nodst or nomem,
> no err retruns back to users any more. Instead, they are taken care
> of by retransmit.
>
> v1->v2:
> - add more details to the changelog in patch 1/6
> - add Fixes: tag in patch 2/6, 3/6
> - also revert 69b5777f2e57 in patch 3/6
Looks good to me, thanks
Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
next prev parent reply other threads:[~2016-09-14 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 18:04 [PATCHv2 net 0/6] sctp: fix the transmit err process Xin Long
2016-09-13 18:04 ` [PATCHv2 net 1/6] sctp: remove the unnecessary state check in sctp_outq_tail Xin Long
2016-09-13 18:04 ` [PATCHv2 net 2/6] sctp: do not return the transmit err back to sctp_sendmsg Xin Long
2016-09-13 18:04 ` [PATCHv2 net 3/6] sctp: free msg->chunks when sctp_primitive_SEND return err Xin Long
2016-09-13 18:04 ` [PATCHv2 net 4/6] sctp: save transmit error to sk_err in sctp_outq_flush Xin Long
2016-09-13 18:04 ` [PATCHv2 net 5/6] sctp: make sctp_outq_flush/tail/uncork return void Xin Long
2016-09-13 18:04 ` [PATCHv2 net 6/6] sctp: not return ENOMEM err back in sctp_packet_transmit Xin Long
2016-09-14 17:16 ` Marcelo Ricardo Leitner [this message]
2016-09-19 2:03 ` [PATCHv2 net 0/6] sctp: fix the transmit err process 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=20160914171605.GG17689@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--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).